One of our users was in concall (he was taken in concall by other party). His call was dropped and the error was displayed as "CM down Features disabled". On Cisco site, they stated that this error comes while making calls. But we saw it immediately after dropping the call. On callmanager, only device unregistered error log has got generated for that IP Phone. What could be the cause? can anything be traceable on CCM server side? Below is link I found on Cisco
Was this phone the only one in the system that had the "CM down" message displayed? Are there any other device unregistrations at around the same time? From the logs, are there any other significant events taking place at around the same time? If other devices unregistered as well, then the cause might have been network or system related. If this one phone was the only one that had a problem, then we could probably focus on what is special or unique about it, such as version of phone load, switch port errors or switch port configuration.
Several IP Phones were unregistered at the same time and only "device unregistered" error log can be seen for these phone. Only one phone was showing CM down error.
All these phones are connected to same 4506 switch and are at remote place from the cluster. This remote place is connected via 45 mbps WAN link. There is no problem seen on any of the IP Phones local to this CCM cluster.
The CM down error shows up when the phone goes into SRST mode while there's an existing call on it. Otherwise they simply transition without much fanfare and if everything is configured correctly, users may never know of the problem.
So the cause of the problem was an event that caused the phones at that site to lose connectivity. The CM down error was just a symptom of the problem. The root cause, however, could have had several likely causes, such as the 45mbps link bouncing, a routing issue resulting momentary loss of connectivity to the site where the CCM cluster is located, a problem on the 4506 switch, etc. So you'd have to do additional investigation to determine the most likely cause.
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...