For CallManagerFailure, Cisco's recommended action is to collect the core file if available plus SDL and CCM/SDI traces from Trace and Log Central and contact Cisco TAC.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- alarms
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 8.5(1) per source
- Checked
- 2026-10-02
Sources
- System Error Messages for Cisco Unified Communications Manager 8.5(1) — Cisco Systems · tier 2 current vendor documentation · CallManagerFailure alarm entry > Recommended Action
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-ccmfailure-tac-data. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-ccmfailure-tac-data
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-ccmfailure-tac-data,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-ccmfailure-tac-data},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-ccmfailure-tac-data},
note = {Source note cucm-high-cpu-troubleshooting-ccmfailure-tac-data, checked 2026-10-02}
}