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 dont want reduce the parameter interdigit timeout value (( in my callmanager TimerT302_msec = 15000 ))
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.
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 )).
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...