Trace Configuration

Table of contents:

Cisco CallManager Serviceability provides a web-based trace tool to assist the system administrator and support personnel in troubleshooting Cisco CallManager problems. Cisco CallManager Serviceability Trace provides three main functions:

  • Configuration This function allows you to configure a variety of options when enabling traces. Options include the level of trace details and the trace file format (.xml or .txt).
  • Analysis and Q.931 Translator These functions allow you to analyze trace files.


    The web-based Trace Analysis tool allows only analysis of Extensible Markup Language (XML) files; the Q.931 Translator analyzes both text and XML files. The XML format adds excessive overhead to the file, and causes the file to contain less information overall than saving the file in another format. For in-depth troubleshooting, Cisco recommends using formats other than XML.

  • Troubleshooting Trace Settings This function allows you to enable troubleshooting traces. With this feature, you can easily set up traces on multiple servers but there are fewer options available than in the Trace Configuration function.

Types of Traces

Traces for Cisco CallManager services can be based on debug levels, specific trace fields, and Cisco CallManager devices, such as phones or gateways. Two types of traces are available, SDI trace and SDL trace.

SDI traces are also known as Cisco CallManager trace log files. Every Cisco CallManager service includes a default trace log file. The system traces SDI information from the services and logs run-time events and traces to a log file. Programmers typically use SDI traces for development purposes.

SDL traces contain call-processing information from Cisco CallManager and Cisco CTIManager services. The system traces the SDL of the call and logs state transitions in a log file. This log information helps administrators to troubleshoot problems on the Cisco CallManager system.


In most cases, extensive SDL traces will be gathered only when Cisco TAC requests it. SDL traces track communication between the CallManagers, whereas SDI traces track internal CallManager processing.


Enabling traces decreases system performance; therefore, enable higher-level trace only for troubleshooting.


Trace Configuration and Analysis Overview

Figure 32-5 provides an overview of trace configuration and analysis options:

  • Troubleshooting trace settings Allows you to enable troubleshooting traces by server and by service for all servers from a single page.
  • Trace configuration Allows detailed trace configuration per server. The configuration options include the trace file format (.xml or .txt).
  • Analysis Allows you to analyze stored trace files (XML only).
  • XML or text editors Allows you to examine the content of the stored trace files.

Figure 32-5. Trace Configuration and Analysis Overview


Trace Configuration

Cisco CallManager provides many services for tracing. You can enable tracing for each service individually for each server within the Cisco CallManager cluster. Perform these tasks in the Cisco CallManager Serviceability Trace Configuration window to configure custom settings for a trace:

Step 1.

In Cisco CallManager Serviceability, choose Trace > Configuration and choose the server where you want to configure the trace settings.


Step 2.

From the Configured Services list, choose the service to change the trace settings, as shown in Figure 32-6. The Trace Configuration window opens. Figure 32-7 displays a sample output of that window.


Figure 32-6. Selecting a Service to Trace


Figure 32-7. Trace Configuration


Step 3.

To enable traces for the specified service, check the Trace On check box.

Step 4.

Choose the desired debug level from the Debug Trace Level drop-down menu.

Step 5.

Choose the trace fields to include in the trace files. This additional information is different for each service.

You can set the path and filename for the trace file. To allow creation of more than one file, Cisco CallManager uses the entered filename and adds an eight-digit string, starting with 00000000, that is incremented with each new file.

Enabling Clusterwide Trace Settings

The Troubleshooting Trace Settings menu item is misleading. This menu item allows you to enable or disable troubleshooting traces on different servers throughout the cluster, as shown in Figure 32-8. This window is usually used for troubleshooting when more than one server needs to be monitored. Each service can be selected or deselected individually for each server.

Figure 32-8. Enabling Traces Clusterwide


Servers and shown in Figure 32-8 are currently offline, which is why the Troubleshooting Trace Setting window shows their services as N/A.

Table 32-2 describes the logging of each service that can be turned on or off in the Troubleshooting Trace Setting window.

Table 32-2. Trace Settings for Multiple Servers



Cisco CallManager

Logs Cisco CallManager signaling information to trace files

Cisco Call Detail Records (CDRs) Insert

Logs information about writing of CDRs

Cisco Certificate Authority Proxy Function (CAPF)

Logs information about issues of Cisco CAPF

Cisco CTIManager

Logs information about issues on CTIManager of the Cisco CallManager

Cisco CallManager

Logs Cisco CallManager signaling information to trace files

Cisco Certificate Trust List (CTL) Provider

Logs information about issues of Cisco CTL Provider

Cisco Database Layer Monitor

Logs information about database usage of Cisco CallManager

Cisco Extended Functions

Logs information about issues referring to any of the Cisco CallManager extended functions, such as Quality Report Tool (QRT)

Cisco CallManager Extension Mobility

Logs information about issues of the Cisco CallManager Extension Mobility service and Extension Mobility application

Cisco IP Manager Assistant (IPMA)

Logs information about issues and usage of Cisco IPMA functionality on Cisco CallManager

Cisco IP Voice Media Streaming Application

Logs information about issues of the Cisco IP Voice Media Streaming Application in conjunction with every involved device

Cisco Messaging Interface

Logs information about issues of Cisco Messaging Interface

Cisco Music on Hold (MoH) Audio Translator

Logs information about issues with MoH on Cisco CallManager

Cisco Real-Time Information Server (RIS) Data Collector

Logs information about issues involving collecting real-time information on Cisco CallManager

Cisco Telephony Call Dispatcher (TCD)

Logs information about issues with attendant consoles and pilot points on Cisco CallManager

Cisco TFTP

Logs information about issues with the TFTP server service of Cisco CallManager

Cisco WebDialer

Logs information about issues with the click-to-dial functionality on Cisco CallManager systems

Trace Analysis

Part I: Cisco CallManager Fundamentals

Introduction to Cisco Unified Communications and Cisco Unified CallManager

Cisco Unified CallManager Clustering and Deployment Options

Cisco Unified CallManager Installation and Upgrades

Part II: IPT Devices and Users

Cisco IP Phones and Other User Devices

Configuring Cisco Unified CallManager to Support IP Phones

Cisco IP Telephony Users

Cisco Bulk Administration Tool

Part III: IPT Network Integration and Route Plan

Cisco Catalyst Switches

Configuring Cisco Gateways and Trunks

Cisco Unified CallManager Route Plan Basics

Cisco Unified CallManager Advanced Route Plans

Configuring Hunt Groups and Call Coverage

Implementing Telephony Call Restrictions and Control

Implementing Multiple-Site Deployments

Part IV: VoIP Features

Media Resources

Configuring User Features, Part 1

Configuring User Features, Part 2

Configuring Cisco Unified CallManager Attendant Console

Configuring Cisco IP Manager Assistant

Part V: IPT Security

Securing the Windows Operating System

Securing Cisco Unified CallManager Administration

Preventing Toll Fraud

Hardening the IP Phone

Understanding Cryptographic Fundamentals

Understanding the Public Key Infrastructure

Understanding Cisco IP Telephony Authentication and Encryption Fundamentals

Configuring Cisco IP Telephony Authentication and Encryption

Part VI: IP Video

Introducing IP Video Telephony

Configuring Cisco VT Advantage

Part VII: IPT Management

Introducing Database Tools and Cisco Unified CallManager Serviceability

Monitoring Performance

Configuring Alarms and Traces

Configuring CAR

Using Additional Management and Monitoring Tools

Part VIII: Appendix

Appendix A. Answers to Review Questions


Authorized Self-Study Guide Cisco IP Telephony (CIPT)
Cisco IP Telephony (CIPT) (Authorized Self-Study) (2nd Edition)
ISBN: 158705261X
EAN: 2147483647
Year: 2004
Pages: 329 © 2008-2020.
If you may any questions please contact us: