CallManager failure, reason code 4, TimerThreadDied, what's it mean?
All the phones re-registered in the network. Below is all I have from the Event log, I don't, at this point, have the full event. The trace showed a reason code 4-TimerthreadDied. Does anyone know what that might mean? What else should I look for? The CM service restarted 10 seconds later, but, 4 minutes later, failed again for over a minute, same reason code.
Also, the D channel dropped for about 10 seconds 3 minutes later.
Error: CallManagerFailure - Indicates some failure in the Cisco CallManager system
Error: kDeviceMgrRegisterKeepAliveResponseError - Cisco CallManager not responding
Error: kDisconnectionToCCM - CMI disconnection with Cisco CallManager.
CallManager Name: The connection with Primary CCM is lost.
Error: CallManagerFailure - Indicates some failure in the Cisco CallManager system.
Did you resolve this issue? We are experiencing a "similar" issue with the error code (TimerthreadDied) on a "clean" install (no configuration) with the CallManager service dieing every couple of minutes the CM is showing the following error code:
%CCM_CALLMANAGER-CALLMANAGER-3-CallManagerFailure: Indicates some failure in the Cisco CallManager system. Host name of hosting node.:SERVER1 IP address of hosting node.:10.3.1.1 Reason code.:4 Additional Text [Optional]: App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:SERVER1
All we have configured are the services to be activated and then this occurs. Any clues?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...