Cisco Systems 30 VIP manual SDL Trace

Page 15

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)

documentation for complete information about turning tracing on and off, and for descriptions of the User Masks and Levels for each configured service, and more.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/admin_gd/admin_gd/inde x.htm

Following are two examples of trace mask bits that would be enabled based on the particular problem.

∙For normal message debugging, turn on subsystem bits 5, 6, 7, 8, 11, and 12

∙For debugging gateways, turn on subsystem bits 3,4,5,6,7,8,9,11,12,13

Following are two examples of desired trace levels based on the particular problem

∙For normal debugging, the trace level should be set to SDI_LEVEL_ARBITRARY

∙For normal running system, the trace level should be set to SDI_LEVEL_ERROR

SDL Trace

Cisco engineers use SDL traces to find the cause of an error. You are not expected to understand the information contained in an SDL trace. However, while working with TAC, you may be asked to enable the SDL trace and provide it to the TAC. SDL trace files can be saved to local directories, the Windows NT Event Viewer, and CiscoWorks 2000. To avoid any performance degradation on the server, be sure that after the trace has been captured, you turn off SDL tracing.

SDL trace provides a C interface to trace and alarms. Alarms are used to inform the administrator of unexpected events, such as being unable to access a file, database, Winsock, or being unable to allocate other operating system resources.

Enabling SDL Trace

SDL traces are enabled in the Service > Service Parameter area in

Cisco CallManager Administration. Remember that these traces should be turned on only when requested by a TAC engineer. Note the values chosen to turn on the SDL trace in the following illustration.

© 2000 Cisco Systems, Inc.

15

Image 15

Contents SDI Trace Output Configuring Traces Reorder Tone Through Gateways Gateway Registration Problems Page Purpose Documentation Checklist Codec Channel Acronym/Term Cnf Law mu-lawChannel Calling Search Space CCAPi Cisco IOS ClusterFlow Full duplex 711 729 225 245 323 Half Duplex Hookflash Jitter Law mu-lawPartition 931 Route Filter Route Group Route List Route PatternSilence Suppression Voice Activation Detection Voice Activation Detection Silence Suppression VoIP Translation PatternCisco CallManager Administration Details View Report Microsoft Performance Microsoft Event Viewer SDI Trace Configuring Traces SDL Trace Page SDLTraceDataFlag Value SDLTraceTypeFlag Value DefinitionCall Detail Records CDR and Call Management Records CMR Sniffer TraceSelect Service Service Parameters CDRs Voice Quality Problem CategoriesPage Packet Number Time absolute ms Time delta ms Button Help John Check Your Loads Phone Resets Dropped Calls Page Page Cisco CallManager Feature Issues Locations Conf Bridge Region1 Region2 MTP Resource Problems MTP Dial Plans Dialing DOES-NOT-EXIST Page DialPlanWizardG Clause NamePattern Device Name Device Description Usage Pattern PartitionReorder Tone Through Gateways Slow Server ResponseGateway Registration Problems Module.port CFG Booting Dhcp for dynamic configurationTracyclose mod port tracystart mod port TaskID Cmd show dhcp Gmsg ***TFTP Error File Not Found Gmsg CCM#0 CPEvent = Loadid -- CPState = LoadResponse Gatekeeper ProblemsRegistration Rejects RRJ Cisco IP Phone Initialization Process Sample TopologyPage Skinny Station Registration Process Acknowledge Station ResetMessage Description Station Register Station IP PortPage Cisco CallManager Initialization Process Self-Starting Processes Cisco CallManager Registration Process Cisco CallManager KeepAlive Process Cisco CallManager Intra-Cluster Call Flow Traces Cisco Systems, Inc CCMStationD stationOutputStopTone tcpHandle=0x4fbbc30 Cisco Systems, Inc Call Flow Traces Page Cisco Systems, Inc Following debug messages show that the call is in progress Gatekeeper Endpoint Registration Debug Messages and Show Commands on the Cisco IOS GatewayCisco Systems, Inc Page Cisco IOS Gateway with T1/PRI Interface Cisco IOS Gateway with T1/CAS Interface Cisco Systems, Inc Inter-Cluster H.323 Communication Call Flow Traces Failed Call Flow Cisco Systems, Inc Reading Records Writing RecordsRemoving Records Table SchemaFields in a Call Detail Record Known IssuesDeciphering the Time Stamp Originator’s node ID Global Call IdentifierOrigination leg call identifier Date/time of call originationPort for the originator’s media connection Isdn location valueCalling party cause Of call termination IP address for the originator’s media connectionCalled party’s partition Destination span or portIP address to which the call was delivered unsigned integer IP port to which the call was deliveredDate/time of disconnect unsigned integer IP address for the destination outgoing media connectionCodec type used by the destination on sending side Date/time of connectDirectory number used on this call Global Call Identifier for this callCisco CallManager node identifier Call IdentifierLost RTP packets during this connection Interarrival jitter during this connectionLatency experienced during this connection Normal Calls Cisco IP Phone-to-Cisco IP Phone Call Management Records Logged By Call Type Codec Cause Codes Description Codec Types Compression / Payload typesNumber changed Alarms Calling Cisco Technical Assistance Center TAC Index Debug messages and show commands Page Topology