have route patterns changed under this release 3.1 3a the reason is I ahve 2 clusters with different version of Cm cluster 1 is running 3.1 and cluster 2 is running 3.1 3a
They have the same route patterns setup.
The problem is I Have a route pattern of 0.0011! and 0.0011!# on CM 3.1.You can match the pattern with the hash to stop the inderdigit time out and coonect the call straight away though under the 3.1 3a release this does dont work its one pattern or the other.
Often times complex troubleshooting issues are best addressed in an interactive session with one of our trained technical assistance engineers. While other forum users may be able to help, its often difficult to do so for this type of issue.
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...