Resumen del contenido incluido en la página 1
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
Cisco IP Telephony Troubleshooting Guide
for Cisco CallManager Release 3.0(1)
Contents
Purpose............................................................................................................................................ 4
Version ............................................................................................................................................ 4
Topology ...............
Resumen del contenido incluido en la página 2
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Conference Bridge.................................................................................................................32 Transcoding Problems...........................................................................................................33 MTP Resource Problems....................................................................................................... 35 Dial Plans .............
Resumen del contenido incluido en la página 3
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Field Data Conversions .........................................................................................................79 Time Values .......................................................................................................................... 79 Deciphering the Time Stamp............................................................................................. 80 IP Addresses...........
Resumen del contenido incluido en la página 4
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Purpose This troubleshooting guide provides descriptions of the tools and utilities used to configure, monitor, and troubleshoot Cisco CallManager Release 3.0(1), Cisco IOS Gateways and Gatekeeper. Appendices provide detailed examples of three different call flows. In the first case study, a Cisco IP Phone calls another Cisco IP Phone within a cluster, which is called an intra- cluster call. In the second case
Resumen del contenido incluido en la página 5
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Documentation Checklist Use the following checklist to be sure you have the proper documentation on your network topology. • Topology that shows all network devices and critical components with port/interface numbers to which they are attached, and what VLAN (if applicable) to which they belong. Special designations should be used for ports that are in trunking or channeling mode. • The root of the spannin
Resumen del contenido incluido en la página 6
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Glossary of Terms Following are some common terms and acronyms that may be used in this document. Glossary Acronym/Term Definition .cnf Configuration file used by devices. μ-law (“mu-law”) Companding technique commonly used in North America. μ-law is standardized as a 64-kbps codec in ITU-T G.711. A-law ITU-T companding standard used in the conversion between analog and digital signals in PCM systems. A-l
Resumen del contenido incluido en la página 7
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Glossary machine, or analog phone attached to a gateway. Examples include 1000, 24231, and so on. DNIS Dialed Number Identification Service. DNS Domain Name System. System used in the Internet for translating names of network nodes into addresses. DRQ Disengage Request. DTMF Dual tone multifrequency. Use of two simultaneous voice-band tones for dialing (such as touch tone). Flow Stream of data traveling be
Resumen del contenido incluido en la página 8
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Glossary PRI PRI is Primary Rate Interface. Primary rate access consists of a single 64-Kbps D channel plus 23 (T1) or 30 (E1) B channels for voice or data. PSTN Public Switched Telephone Network. General term referring to the variety of telephone networks and services in place worldwide. Q.931 ITU standard that describes ISDN signaling. The H.225.0 standard uses a variant of Q.931 to establish and disconnect
Resumen del contenido incluido en la página 9
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Glossary 1.544 Mbps through the telephone-switching network, using AMI or B8ZS coding. CAS is a Channel Associated Signaling interface. T1/PRI T1 is a digital WAN carrier facility, transmitting DS-1-formatted data at 1.544 Mbps through the telephone-switching network, using AMI or B8ZS coding. PRI is Primary Rate Interface. Primary rate access consists of a single 64-Kbps D channel plus 23 (T1) or 30 (E1) B
Resumen del contenido incluido en la página 10
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Tools and Utilities to Monitor and Troubleshoot Cisco CallManager This section addresses the tools and utilities to configure, monitor and troubleshoot Cisco CallManager. Cisco CallManager Administration Details Cisco CallManager Administration provides version information for the system, database and other components. On the opening page, press the Details button and write down the versions in use. A
Resumen del contenido incluido en la página 11
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Microsoft Performance Performance (Monitor) is a Windows 2000 server application that can display the activities and status of your Cisco CallManager system. It reports both general and specific information in real time. You can use Windows 2000 Performance to collect and display system and device statistics for any Cisco CallManager installation. This administrative tool allows you to gain a full understandin
Resumen del contenido incluido en la página 12
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Microsoft Event Viewer Microsoft Event Viewer is a Windows NT Server application that displays system, security, and application events (including Cisco CallManager) for the Windows NT Server. If a service (including TFTP) cannot read the database (where it gets the trace configuration), it will add errors to the Event Viewer. The Event Viewer is the only place where these types of errors will appear. The fol
Resumen del contenido incluido en la página 13
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Detailed Information about Events You can double-click an event in the log to learn more information about the event. SDI Trace SDI traces are local log files. The IP address, TCP handle, device name or the time stamp can be used when reviewing the SDI trace to monitor the occurrence or the disposition of a request. This device name could be tracked back to the building of the file, which shows the devic
Resumen del contenido incluido en la página 14
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) need—and only the information you need—it’s important to understand how to set the options on the trace configuration interface. The trace files are stored in the following default location: C:\Program Files\cisco\bin. A new trace file is started each time Cisco CallManager restarts, or when the designated number of lines has been reached. Following is an illustration of the Cisco CallManager Administrat
Resumen del contenido incluido en la página 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 subsyst
Resumen del contenido incluido en la página 16
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Once SDL traces are enabled, collect the traces. If the traces are being sent to the local drive, then you can retrieve them in the Cisco\Trace subdirectory. Alternatively, the trace files can be sent to an event log or to CiscoWorks 2000. SDL flag bits described in the following table are set in the Service > Service Parameters area in Cisco CallManager Administration. Following are two examples of desir
Resumen del contenido incluido en la página 17
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) SdlTraceTypeFlags Definitions SDLTraceTypeFlag Value Definition traceLayer1 = 0x00000001 All Layer 1 trace on TraceDetailLayer1 = 0x00000002 Detail Layer 1 trace on TraceSdlLinkAdmin = 0x00000004 Trace inter-Cisco CallManager links within a cluster traceUnused = 0x00000008 Not used traceLayer2 = 0x00000010 All Layer 2 trace on traceLayer2Interface = 0x00000020 Layer 2 interface trace on traceLayer2TCP = 0
Resumen del contenido incluido en la página 18
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) Sniffer Trace A Sniffer is a software application that monitors IP traffic on a network and provides information in the form of a trace. Sniffer traces provide information about the quantity and type of network traffic on your network. TCP/IP or UDP packets are protocols utilized by Cisco CallManager and endpoint devices such as phones and gateways. Sniffer traces can also help you identify high levels of broa
Resumen del contenido incluido en la página 19
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) • List of fields contained in each record and a description of what that field represents • Description of the types of calls logged, and the fields logged with each of them • List of cause codes that may appear in the CDR records Enabling or Disabling CDRs CDR record creation is disabled by default when the system is installed. If you wish to have CDR data, you must enable CDRs in the Service > Service Para
Resumen del contenido incluido en la página 20
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1) 7. Update. Result: Call Detail Records will start logging immediately. Caution: Tracing voice connectivity requires that CDR logging be enabled on every Cisco CallManager installation in a cluster. CDRs CDRs provide basic information that can help you understand the more detailed information contained in SDI traces. Basic CDRs provide information such as the calling number, called number, originatin
