I have installed a number of ATA 186 devices running 2.15 MGCP software version. They are using DHCP and are registering with a local call manager. The ATA's get an IP address correctly and when configured on Call Manager register as usual. However on watching the phone list I can see the ATA going from registered to not registered state every minute or so.
Sniffing the port of the ATA shows lots of DNS resolves for the Call manager. It also fails to find the .cnf.xml file. This is strange as browsing on the call manager the file exists. I also can't see any problems with the DNS entries etc.
Found the answer. The ATAs were trying to register their second port (which I had not configured in Call Manager. After a couple of attempts at trying to tft[p their ATA.cnf.xml files they unregistered with call manager and tried again. Adding the second port into CM fixed the 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...
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...