cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
472
Views
0
Helpful
5
Replies

Delay in Call Establishment

Hi,

I have updated my callmanager to 3.2(1) add I have added the service Path cisco callmanager 3-2-1-spB.

With the old version I use the octothorpe (#) key to signal the end of the dialing Sequence (( to signal that the last digit has been entered )) and my call has establishes immediately, without a delay of 15 Sec.

Now with the new version when I added the octothorpe (#) key I have always a busy tone.

Note : I don’t want reduce the parameter interdigit timeout value (( in my callmanager TimerT302_msec = 15000 ))

there are someone can help me

Best Regards :-).

5 Replies 5

joe.leo
Level 1
Level 1

Make a new route pattern. Examlpe:

9.XXXXXXX

(ie. 9 to enable outoging calls, X for any digit, here I use 7-digit phone number)

Hi,

I have a route pattern 98XXXXXX configurate in my callmanager and the Directory Number of the operator is 9 So I have this delay when I try to call the operator.

Before updating my system, to call the operator I put 9 # and my call is dispatch directly but now I must await 15 sec if I Want call here.

Because if I put 9 # I obtein always a busy tone.

Best Regards

Hi,

I think you may have a bit of a conflict here. You may confusing the call Manager by using 9 to seize a voice trunk and also using it as the operator number. Change the operators number to 0 or configure a translation pattern for 0# that maps directly to your operator's extension.

Let me know how this works out.

Ade

Hi,

I don't want change the Directory number of operartor and translation pattern don't resolve my problem because I have different pattern with different length in the same calling search space (( 9 and 98XXXXXX )).

with a last version (( cisco callmanager 3.1 )) after I put 9, I added the octothorpe (#) key and my call is dispatch directly as it is mentioned in this document : http://www.cisco.com/warp/public/788/AVVID/interdigit_timeout.html .

But now with new version of cisco callmanage (( cisco callmanager 3.2.1 )) when I add the octothorpe (#) key I have a Busy Tone.

Best Regards

Hi,

What I am referring to here is a translation pattern and not a route pattern. If you are getting problems with the octothorpe, try putting in a translation pattern for 9# (or whatever you are using). Configure the translation pattern to discard the trailing # and set the transform mask to your operator's number.

I use CCM 3.1.3a with a similar translation pattern and it works fine. I think it may work with 3.2 as well.

Also, are the calls you make IP phone to IP phone? Are they both registered with the same CCM? If they are, you do not need # to cancel the interdigit timeout period. Call manager will collect the digits and connect the call almost instantaneously because it recognises the number (line) as being connected to it.

Regards,

Ade