Traces provide detailed information about specific services and functions on Cisco Unified Communications Manager and that can be useful for troubleshooting call failures on the system.
This document covers the procedure on how to configure the Cisco Call Manager Traces on CUCM 8.x.
1. First navigate to the Unified Serviceability page (https://cucm/ccmservice).
2. To configure Traces,
Go to Cisco Unified Serviceability. Click on Trace> Configuration:
Select the Server and other fields from drop-down list and click Go
Server* - 192.168.1.8 -> Go
Services Group* - CM services -> Go
Service* - Cisco CallManager (Active) -> Go
3. Check “Trace on” to enable the Trace
4. Go to “Trace filter settings” and specify the desired “Debug Trace level” from Drop-down
We must select the boxes based on the requirement and the trace settings can be configured for debugging any particular feature/services/call failure. Multiple options can also be enabled.
For most relevant information related to the issue in your network, select only the required trace to include only the desired information on the debugs.
Table: Field name and description
Enable H245 Message Trace
Activates trace of H245 messages.
Enable DT-24+/DE-30+ Trace
Activates the logging of ISDN type of DT-24+/DE-30+ device traces.
Enable PRI Trace
Activates trace of primary rate interface (PRI) devices.
Enable ISDN Translation Trace
Activates ISDN message traces. Used for normal debugging.
Enable H225 & Gatekeeper Trace
Activates trace of H.225 devices. Used for normal debugging.
Enable Miscellaneous Trace
Activates trace of miscellaneous devices.
Note Do not check this check box during normal system operation.
Enable Conference Bridge Trace
Activates trace of conference bridges. Used for normal debugging.
Enable Music on Hold Trace
Activates trace of music on hold (MOH) devices. Used to trace MOH device status such as registered with Cisco Unified Communications Manager, unregistered with Cisco Unified Communications Manager, and resource allocation processed successfully or failed.
Enable Unified CMReal-Time Information Server Trace
Activates Cisco Unified Communications Manager real-time information traces that the real-time information server uses.
Enable SIP Stack Trace
Activates trace of SIP stack.
Note Enabling SIP Stack Trace can cause extreme performance degradation especially during high traffic hours.
Enable Annunciator Trace
Activates trace for the annunciator, a SCCP device that uses the Cisco IP Voice Media Streaming Application service to enable Cisco Unified Communications Manager to play prerecorded announcements (.wav files) and tones to Cisco Unified IP Phones, gateways, and other configurable devices.
Enable CDR Trace
Activates traces for CDR.
Enable Analog Trunk Trace
Activates trace of all analog trunk (AT) gateways.
Enable All Phone Device Trace
Activates trace of phone devices. Trace information includes SoftPhone devices. Used for normal debugging.
Enable MTP Trace
Activates trace of media termination point (MTP) devices. Used for normal debugging.
Enable All Gateway Trace
Activates trace of all analog and digital gateways.
Enable Forward and Miscellaneous Trace
Activates trace for call forwarding and all subsystems that are not covered by another check box. Used for normal debugging.
Enable MGCP Trace
Activates trace for media gateway control protocol (MGCP) devices. Used for normal debugging.
Enable Media Resource Manager Trace
Activates trace for media resource manager (MRM) activities.
Enable SIP Call Processing Trace
Activates trace for SIP call processing.
Enable SCCP Keep Alive Trace
Activates trace for SCCP keepalive trace information in the Cisco CallManager traces. Because each SCCP device reports keepalive messages every 30 seconds, and each keepalive message creates 3 lines of trace data, the system generates a large amount of trace data when this check box is checked.
Enable SIP Keep Alive (REGISTER Refresh) Trace
Activates trace for SIP keepalive (REGISTER refresh) trace information in the Cisco CallManager traces. Because each SIP device reports keepalive messages every 2 minutes, and each keepalive message can create multiple lines of trace data, the system generates a large amount of trace data when this check box is checked.