Call connection delay

[popolou]

Is there a timer or flag that controls the wait after the digits have been dialled and the outgoing call rings? Upgrading to V6 PR4 seems to have introduced a pause during this time which is making users think the call has failed.

Cheers
Pops

[acejavelin]

Check your Interdigit Long/Short timers in Timers and Limits, they should be 15 seconds/4 seconds respectively... From the system docs:

Used in determining end of dialing. Short timer is used after a valid number has been dialed. Long timer is used until digits form a valid number.

Note if you are using ARS, this may be an indication of an incorrect digit match pattern, or conflicting ones.

[popolou]

Cheers AJ. I'm wondering whether the system is now always waiting for the Long Timer to expire before triggering the short timer. That would be approximately the same wait time that i've heard from the users.

But i see your point on ARS - presumably if it has to wait for the expiry of the LT then this perhaps is implying that it is not detecting a valid number combination? Odd really, nothing has changed with the routing but i'll take a look.

Rgds
Pops

[dwayneg]

If you're in an area where 7-digit dialing is allowed the long timer is going to kick in...once you dial 7 digits it needs to wait to see if you're going to dial more before trying to route call.  Shortening timer will help this, but if a user hesitates in dialing a 10 digit number it will stop waiting and try to process as local.  If you are using 7 digits, try this: dial the number, then press pound.  This over-rides timer and tells system to route what you've dialed.  If this solves it it's time to start reducing the SHORT timer...this is the timer used after a valid number (7 digits) is dialed to wait for additional digits.  Long timer is only used until system sees a valid number (7 digits).

[popolou]

If you're in an area where 7-digit dialing is allowed the long timer is going to kick in...once you dial 7 digits it needs to wait to see if you're going to dial more before trying to route call.  Shortening timer will help this, but if a user hesitates in dialing a 10 digit number it will stop waiting and try to process as local.  If you are using 7 digits, try this: dial the number, then press pound.  This over-rides timer and tells system to route what you've dialed.  If this solves it it's time to start reducing the SHORT timer...this is the timer used after a valid number (7 digits) is dialed to wait for additional digits.  Long timer is only used until system sees a valid number (7 digits).

Cheers, interesting to learn of this. Any UK local number in their shortest form is comprised of 8 digits, while 11-digits are commonly used in their 'long' form. Therefore i presume that we'd almost never hit the short timer and instead the system is either trying to match against ARS or timing out (and so signifying an ARS issue) according to the long timer.

This has given me food for thought. I'm going to test tomorrow and post back.

Thanks both.
Pops

[popolou]

Hmm, seems there is more to this than I thought. I am finding a good deal of M4000 WRN DB CP Numbering Plan Analysis: No Match With Table For x errors in the message print which appears to imply that there are indeed errors with the ARS. However, reading up on the error I find this: -

Cause: The software was searching for the specified object in the specified table and didn't find it. This indicates some form of software error. The software tried to handle the situation in a reasonable manner to continue service.

Action: Save the database. From Diagnostics Monitor/System Monitor, dump the “Numbering Plan Analysis” table via Database Records. Capture this information and send a report to Mitel Field Service.

I recreated the numbering plan but it doesn't seem to fix it. Also, I cannot find how to dump the analysis or any sign of Database Records. Any idea where this could be or is this specialised diagnostic equipment?

Suspect I may need to refer this up the chain.... 

Pops

[NTEDave]

Dialling a # at the end of the number overrides the timer and send the digits out straight way (ish)

[619Tech]

"I recreated the numbering plan but it doesn't seem to fix it. Also, I cannot find how to dump the analysis or any sign of Database Records. Any idea where this could be or is this specialised diagnostic equipment?"

Popolou - The dump is done via the Diagnostic Monitor Program:
1. Via Session Manager - Make sure User Level System Monitor is enabled in "Sockets".
2. Launch Diagnostic Monitor & create a System Monitor Connection.
3. At the top click on System Monitor, which gives a drop down to several items including "Dump Database Records", from there you will get to choose the records to dump.

[popolou]

Thanks 619, I thought that mention of System Monitor and Diagnostic Monitor was familiar - the last time I used it was with the v3.2 firmware. It appears that Mitel do not bundle it with recent SysAd packages so I don't have access to it.

It is beginning to dawn on me that there is an error with the software (DB checks out fine) and so while searching on other's experiences i found similar references that implied it was a CF card fault. I just need to get hold of the dumps to establish this which is the first hurdle.

Rgds
Pops