For a CallManager resource interruption, Cisco recommends collecting Cisco CallManager and SDL traces from 15 minutes before to 15 minutes after the interruption, plus perfmon traces; if none exist, start perfmon tracking of per-process CPU and memory.
Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- CallManager service
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 12.5(1)
- Checked
- 2026-10-02
Sources
- Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Cisco Unified Communications Manager System Issues — Cisco Systems · tier 2 current vendor documentation · Cisco Unified Communications Manager System Stops Responding > recommended actions
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-ccm-outage-collect-15-min. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-ccm-outage-collect-15-min
BibTeX
@misc{warmtransfer-claim-cucm-high-cpu-troubleshooting-ccm-outage-collect-15-min,
title = {Troubleshooting high CPU and service crashes in Unified CM: source note cucm-high-cpu-troubleshooting-ccm-outage-collect-15-min},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-high-cpu-troubleshooting-ccm-outage-collect-15-min},
note = {Source note cucm-high-cpu-troubleshooting-ccm-outage-collect-15-min, checked 2026-10-02}
}