Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Trace

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/adminGd/cucm_b_administration-guide-15/cucm_b_test-adminguide_chapter_011000.html

Published

2026-08-31

Updated

unknown

Accessed

2026-09-22

HTTP status

200

License

Cisco copyright; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Trace settings for a service can be applied to every server in the cluster by checking Apply to All Nodes, with the Trace On check box enabling tracing. in context
• Before increasing CallManager trace file count or size during an incident, the existing SDL files should be collected first, because the change deletes all but the current file. inferred in context
• Because SDL files roll over in a fixed-size ring, the time window an SDL collection can cover depends on call volume and the configured file count and size, so traces for a past incident may already be overwritten. inferred in context
• The Detailed trace level traces all Arbitrary conditions plus detailed debugging information. in context
• CUCM service debug trace levels are cumulative in the order Error, Special, State Transition, Significant, Entry/Exit, Arbitrary, Detailed, each level tracing everything the previous level does plus more. in context
• Trace Output Settings expose Maximum No. of Files (total trace files for a service) and Maximum File Size in megabytes; the release 15 guide says their defaults vary by service and does not print CallManager values. in context
• Changing Maximum No. of Files or Maximum File Size causes the system to delete all service log files except the current file. in context
• Reset Troubleshooting Traces restores the original trace settings for the services on the chosen node. in context
• When the last trace file in the sequence is full, trace data begins writing over the first file, so the oldest trace data is lost. in context
• The Cisco CallManager SDL configuration trace characteristics include Enable SDL link states trace, Enable low-level SDL trace, Enable SDL TCP event trace and Disable pretty print of SDL trace. in context
• In CUCM release 15, SDL stands for Signaling Distribution Layer trace and is supported for the Cisco CallManager and Cisco CTIManager services on Unified Communications Manager only. in context
• The Cisco CallManager SDL configuration trace filter settings include Enable all Layer 1 traces, Enable all Layer 2 traces, Enable Layer 2 interface trace, Enable all Layer 3 traces and Enable all call control traces. in context
• The Cisco CallManager trace filter Enable SIP Call Processing Trace activates trace for SIP call processing. in context
• Enable SIP Keep Alive (REGISTER Refresh) Trace activates trace of SIP REGISTER refresh keepalives and Cisco warns it generates a large amount of trace data. in context
• The Cisco CallManager trace filter Enable SIP Stack Trace activates trace of the SIP stack and is enabled by default. in context
• Trace and Log Central, an option in Cisco Unified RTMT, is the documented tool to collect, view and zip service traces and other log files. in context
• Cisco Unified Serviceability supports three trace kinds: SDI (System Diagnostic Interface) trace, SDL trace, and Log4J trace for Java applications. in context
• Troubleshooting Trace Settings backs up the original configuration and applies predetermined troubleshooting trace settings; leaving it enabled for a long time increases trace file size and may affect service performance. in context

Cite this source record

APA

WarmTransfer. (2026, August 31). Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Trace. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-admin-15-trace

BibTeX

@misc{warmtransfer-cisco-cucm-admin-15-trace,
  title  = {Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Trace},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-admin-15-trace},
  note   = {Cisco Systems, accessed 2026-09-22}
}