Have a Magix 4.0 with a PRI set for 5ESS, the customer has to wait 5-7 seconds before outbound local and long distance calls are connected. If the customer uses a # sign at the end of the dialing sequence it connects the call right away. The carrier says they have their switch set to route the digits within 1 second. Seems the issue is on the Magix side. There is only one pool with the 23 PRI trunks specificied in ARS. There are no other lines or other pools. Any ideas? Is there a timer setting somewhere?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Magix PRI outbound dialing takes a long time
- Thread starter qtelcom
- Start date
dagwoodsystems
Programmer
Do a printout of SYSTEM SETUP and look at the line that says "Inter-digit Timers". The last value in that row should be 5. Actually, check 'em all. It should look like this:
Tim Alberstein
Code:
Inter-digit Timers (seconds) : 5 24 24 10 10 10 10 5 5Tim Alberstein
- Thread starter
- #3
TouchToneTommy
Vendor
Look at those interdigit timers. You have to find a happy medium. If the first timer is for the time between the 1st and 2nd digit (and I don't know that to be the case, you'd have to experiment, and you should DOCUMENT the settings, and BACKUP the switch before changing them, in case you need to go back), then it says 10 seconds after the 7th digit is dialed the Magix assumes you're done and sends the call out on the appropiate route. 5 seconds after the 10th digit.
Dialing # says to the Magix "I'm done! Send out the call!"
So, either train the users to press # at the end, or see if you can find the correct timer, and find a setting that doesn't create more problems, and report back what works!!
Dialing # says to the Magix "I'm done! Send out the call!"
So, either train the users to press # at the end, or see if you can find the correct timer, and find a setting that doesn't create more problems, and report back what works!!
The reason the Legend/Magix works like that is because of the way the PRI works. All call setup and teardown is done on the DCH or D (data) channel. So the switch can't do any of this until it has all the digits for the call. Once that happens the call is processed and the path is established and ringing, etc.
If they are impatient, tell them to press #!
....JIM....
If they are impatient, tell them to press #!
....JIM....
- Thread starter
- #6
I guess what's interesting is the customer had a t-1 and switched to a PRI. They experienced none of these timing issues with the T-1, so they really notice the delay now. I've trained them the # way, as the interdigits would probably cause more problems than it's worth. Too bad you can't tell the magix to look for 9 plus 7 digits and then immediately send the call, and look for 9 + 1 plus 10 digits and immdediately send the call. Of course... IPOffice can do this... 
Thanks for everyone's help and explanation though!
Thanks for everyone's help and explanation though!
dagwoodsystems
Programmer
The only other time I see this behavior is when a PRI goes through an IP or other packet based network. I've never seen this kind of slowness with a traditional circuit-switched PRI. Any chance this new service is being delivered by IAD or router?
Not all H.323 devices support "overlapped sending" (digits are processed as the PBX sends them out) This looks more like "en bloc", except that a termination key isn't required. If sent, # indicates the end of the string. Otherwise, the telco hardware waits for a timer to expire before declaring that all digits have been sent.
Your inter-digit timers are correct, but you might try one little tweak. This will help things slightly, but is by no means an indication that your PBX is at fault here. Go to System Program > Start > Options > More > Inter-digit and choose timer #9 (the last one). Change that value from the default of 5, and make it a 3 instead. Note that this also changes how much time you have to dial a subsequent digit. If you dial a phone number too slowly, the attempt will get kicked and you'll have to try again. The trade-off is that this should shorten the apparent call setup time by two seconds.
Programming the switch to immediately send a "#" once a specific number of digits is collected would certainly help in this case (at least in North America). You'd still need to manually dial # for International calls due to variable number lengths.
Tim Alberstein
Not all H.323 devices support "overlapped sending" (digits are processed as the PBX sends them out) This looks more like "en bloc", except that a termination key isn't required. If sent, # indicates the end of the string. Otherwise, the telco hardware waits for a timer to expire before declaring that all digits have been sent.
Your inter-digit timers are correct, but you might try one little tweak. This will help things slightly, but is by no means an indication that your PBX is at fault here. Go to System Program > Start > Options > More > Inter-digit and choose timer #9 (the last one). Change that value from the default of 5, and make it a 3 instead. Note that this also changes how much time you have to dial a subsequent digit. If you dial a phone number too slowly, the attempt will get kicked and you'll have to try again. The trade-off is that this should shorten the apparent call setup time by two seconds.
Programming the switch to immediately send a "#" once a specific number of digits is collected would certainly help in this case (at least in North America). You'd still need to manually dial # for International calls due to variable number lengths.
Tim Alberstein
- Status
Similar threads
- Locked
- Question
- Locked
- Question