If you had more than one primary Cisco Unified CallManager server in a cluster and you are upgrading from Cisco CallManager Release 3.3(x), to Cisco Unified CallManager 4.3(1), you will need to reassign the route list to the Cisco Unified CallManager group that you configured in Cisco Unified CallManager Administration to maintain optimal load balance. To ensure call processing redundancy, the upgrade program created a Cisco Unified CallManager group containing a primary server and a backup server for every primary Cisco Unified CallManager server in the cluster and then assigned route lists to each Cisco Unified CallManager group using a round robin algorithm. The name format for the created Cisco Unified CallManager group is RLCMG_.
Step 1 Evaluate the Cisco Unified CallManager group and route list configuration for load balancing and redundancy, as described in the Cisco Unified CallManager System Guide and the Cisco Unified CallManager Network Solutions Design Guide.
Step 2 Assign the route list(s) to the Cisco Unified CallManager group(s) that you have configured in Cisco Unified CallManager Administration.
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...