On CCM 3.1, if you use the @ in your route patterns, you can get about 300 in before it causes serious problems. After 300, if you add or update any route pattern the CPU will hit %100 for about 1 minute and sometimes CCM service will quit. You can insert a longer database initialization time in the service parameters and get about 1000 route patterns in, but each add will take down the service and you will have to do on off-hours. If you don't use the @ in your route pattern, it doesn't seem to cause problems although CPU will still spike for a few seconds when updating route patterns. Have not tried 3.2 with 1000 route patterns yet.
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...
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 discusses the bas...