In CallManager 4.2 alarm documentation, CodeRedEntry means CallManager could not recover even after call throttling and the CallManager service is shut down; the recommended action is to find the cause of high CPU in the High and Normal priority queues.
Checked 2026-10-02
CallManager is not able to recover, even after attempting call throttling. The CallManager service is shut down.
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- call throttling
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 4.2 only; current-release Code Red behaviour not verified
- Checked
- 2026-10-02
Sources
- System Error Messages for Cisco Unified CallManager 4.2 — Cisco Systems · tier 2 current vendor documentation · CodeRedEntry alarm entry
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-codered-v42-definition. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-codered-v42-definition
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-codered-v42-definition,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-codered-v42-definition},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-codered-v42-definition},
note = {Source note cucm-high-cpu-troubleshooting-codered-v42-definition, checked 2026-10-02}
}