The following is an error in the application event log. Approximately 2 hours after this call manager locked up and I was unable to access it at the conslole and had to reboot server. CM 3.3(2) There were no other entries between the following entry and when I rebooted. My 1st indication that something was wrong was calls were not forwarding to voice mail (Unity 4.0(2)
Event Type: Error
Event Source: Cisco IP Voice Media Streaming App
Event Category: None
Event ID: 3
Time: 10:27:30 AM
Error: kDeviceMgrLockoutWithCallManager - Cisco CallManager in lockout.
Trace Name: [MTP][10.12.0.1]
App ID: Cisco IP Voice Media Streaming App
Cluster ID: CM1-Cluster
Node ID: 10.12.0.1
Explanation: The specified Cisco CallManager is in a lockout until it responds or terminates the TCP link. The Cisco CallManager will not be used.
Recommended Action: To force CallManager out of lockout, restart Cisco CallManager service..
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...
[toc:faq]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 discusse...