I just installed my first Callmanager cluster for a customer. Everything went fine, except the installation of the vg200. It took some time, until i found the right image to use(12.2.2(XM)). After using this image the configuration was very easy(ccm-manager config-download). :)
But now to my problem. If i start the vg200, using this configuration:
enable secret mdhl
ip address 172.17.12.6 255.255.254.0
ip route 0.0.0.0 0.0.0.0 172.17.12.1
line vty 0 4
ccm-manager config server 172.17.12.9
, the vg200 is downloading it's configuration from the callmanager and is registering fine, with the primary callmanager. show ccm-manager looks fine and the callmanager is also saying, that this interface has registered.
After the download of the configfile, the vg200 save it's configuration as startup-config.
After next reboot, the vg200 is NOT able to register with a callmanager anymore! It's is still downloading it's configuration, show ccm-manager looks also fine(it says it is registered), but if i look at the status page in the callmanager, it says that it is not registered. And if the callmanager thinks, that the vg200 is not registred, i can't use it.
If i apply the configuration above again, its booting up, downloads its configuration and registers fine.
What is the MGCP domain name of this gateway as it appears in CallManager? Make sure since in your VG200 config you have not included the ip domain-name, that you accordingly in CallManager have set the gateway's name to just mdhl-vg200-2
If that is not the problem, you should open up a case withe Cisco TAC. I have not seen this before.
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...