I was reading in the SRND guide that if you have a SIP trunk defined in callmanager, the way you get CM redundency is thru dial-peers so you point the first dial peer to the primary callmanager and a second dial peer to the backup callmanager.( page 4-17 of the 01/08 CM6)
This is the first I seen this and this is not the way we have done our deployments.
The config we have is cm 5.1.3, IPCC enterprise 7.X and CVP ver 4.1. SIP is the preferred way for connections.
As anyone setup their dial-peers like I mentioned in the SRND guide.. page 4-17 of the 01/08 CM6
I asked some of our local guys and this is new to them ...
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...