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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems with Dial Delay Time

Status
Not open for further replies.

IThack

IS-IT--Management
Nov 4, 2005
49
GB
I'm using a 406 V2. Has been working reasonably well with 3.0, and 3.1 (48), but 3.2 doesn't.

I have 4 channels of ISDN, and 5 channels of IP trunks (H323). I am using a shortcode of [0]N; The ";" is needed, so that the full number is sent to the IP trunk (or another IPO using SCN). This works with 3.1.48, but 3.1.65 & 3.2 doesn't.

When upgrading from 3.1.48 to 3.1.65, and no changes to the config, I get this:

CMTARGET: OVERLAP LOOKUP CALL ROUTE:2 returned 0

I've checked the shortcuts, and I can't find any problem.

This "error" happens with calls over ISDN, as well as SCN to another IPO and the IP trunk. I've tried changing the config to ISDN only, and it's the same. Regrade to 3.1.48 and it works fine.

The system waits for 30 seconds, and then drops the outgoing call request. But if I dial # after the number, the call is placed correctly. So it seems that the dial delay time is wrong. I checked it, and it's 3 seconds.

I've tried removing LCR (used to "failover" when ISDN is full). I've tried removing and /or editing shortcodes. Perhaps I'm doing something wrong, but why does it work with one verison and not others.

Does anyone else use ";" in shortcodes? Does anyone use that feature, and use 3.1.65+ firmware? Any help debugging this will be very appreciated.
 
I use it in the us but we are using [9]0N; and it works fine on everything 3.0-3.2. Are you just dialing 0then then rest or do you use scondary dialtone?
 
Just dial the number. No secondary tone. I also have [9]0N; in case someone is used to dialling a 9 first. Both have the same result, and need # to complete the call.

There must be something else that's different. Perhaps I'm not understanding how it decides on a call route.
 
Since 3.1 the ; is not needed anymore on IP trunks to other IP Offices.
Your problem may be the dial delay count and dial delay time.
For the ; option to work prperly thr dial delay count must be 0 and the dial delay timer must be 3 seconds ore more.
 
I am using a delay of 3 seconds and a count of 3. If I don't use the ; it just sends 3 of the idalled digits to the IP trunk. So the result is a wrong number.

I'm using 3 digit extensions, so I've set the count to 3. Are you saying that it will work with a count of 0 ? I'll try it and see what the result is.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top