atcomsystems.ca/forum
Hello.

I've read this post HERE and have basically the same problem.

We have multiple incoming analog trunks and need some method to re-connect to the same trunk after a crank call so we can dial *57. I've tested this at reception using direct trunk access to re-connect to the trunk indicated in the reception console display (ie trunk 109) and then dial *69, but the trunk is invariably in use already, or connects to an incoming call on that trunk.

The Telco provides a terminal hunt so the trunk is in use right away after hang up. There are 7 incoming trunks.

I though of asking the Telco to change to circular hunt but we have, on several occasions, needed the terminal hunt to identify a bad trunk.

Any other suggestions for identifying or marking a crank caller?
Tough one - if it's the first trunk then it may be difficult - if not put the trunks in terminal hunt for outgoing from the last to the first trunk. This way if the trunk is near the top it will minimize someone hitting it for outgoing. Like I said if it is the first trunk it could be tough due to incoming traffic. Don't know if the telco can be of any assistance in tracking the traffic. If they can then the property can note the trunk number and exact time of the call and that should be all the telco needs once you determine which trunk corresponds to telco trunks. Can't think of much else.
You could also explain to telco what is going on - have them put trunks in circular hunt until you identify the perpetrator then have them put back to terminal
Quote
Originally posted by Dane:
Tough one - if it's the first trunk then it may be difficult - if not put the trunks in terminal hunt for outgoing from the last to the first trunk. This way if the trunk is near the top it will minimize someone hitting it for outgoing. Like I said if it is the first trunk it could be tough due to incoming traffic. Don't know if the telco can be of any assistance in tracking the traffic. If they can then the property can note the trunk number and exact time of the call and that should be all the telco needs once you determine which trunk corresponds to telco trunks. Can't think of much else.
No problem with outgoing calls picking up the trunk as they're different physical trunks than the incoming ones.

Regarding noting the trunk number and time, this sounds like a possibility but I wasn't aware that the Telco could trace a call just based on the number and time. I thought they needed the recipient to dial *57 to 'mark' the call.
oh well - gonna be topugh then
Quote
Originally posted by Dane:
You could also explain to telco what is going on - have them put trunks in circular hunt until you identify the perpetrator then have them put back to terminal
We're looking for a permanent solution that may in fact not be used for 6 months. Regardless, I suppose we could go to circular hunt and then back to terminal temporarily if there's a suspected problem with one of the lines. Line problems we have are because we're at the end of a long run from the Telco and about once a year on average, experience a wet or corroded trunk line causing echo, dropouts, or static etc.
© Sundance Business VOIP Telephone Help