Download Print this page

Cisco 30 VIP Troubleshooting Manual

For cisco callmanager release 3.0(1).
Hide thumbs

Advertisement

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
Contents
Purpose ............................................................................................................................................ 4
Version ............................................................................................................................................ 4
Topology ......................................................................................................................................... 4
Documentation Checklist ............................................................................................................ 5
Glossary of Terms ........................................................................................................................... 6
Tools and Utilities to Monitor and Troubleshoot Cisco CallManager.......................................... 10
Cisco CallManager Administration Details .............................................................................. 10
Microsoft Performance.............................................................................................................. 11
Opening Microsoft Performance........................................................................................... 11
Customizing Performance ..................................................................................................... 11
Microsoft Event Viewer ............................................................................................................ 12
Opening Event Viewer .......................................................................................................... 12
Detailed Information about Events ....................................................................................... 13
SDI Trace .................................................................................................................................. 13
SDI Trace Output .................................................................................................................. 13
Configuring Traces................................................................................................................ 14
SDL Trace ................................................................................................................................. 15
Enabling SDL Trace.............................................................................................................. 15
Disk Space Warning.............................................................................................................. 17
Sniffer Trace.............................................................................................................................. 18
Sniffer Trace Applications .................................................................................................... 18
Call Detail Records (CDR) and Call Management Records (CMR) ........................................ 18
Enabling or Disabling CDRs................................................................................................. 19
CDRs ..................................................................................................................................... 20
Diagnostic CDRs (Also Known As CMRs).......................................................................... 20
Problem Categories ....................................................................................................................... 21
Voice Quality ............................................................................................................................ 21
Lost or Distorted Audio......................................................................................................... 21
i Button Help ......................................................................................................................... 24
Crackling ............................................................................................................................... 25
Check Your Loads................................................................................................................. 25
Echo....................................................................................................................................... 25
Check Your Loads............................................................................................................. 26
One-Way Audio or No Audio ............................................................................................... 26
MTP and One-Way Audio .................................................................................................... 27
Phone Resets ............................................................................................................................. 27
Dropped Calls............................................................................................................................ 28
Check Your Loads................................................................................................................. 31
Cisco CallManager Feature Issues ............................................................................................ 31
Codec/Regions: Codec Mismatch ......................................................................................... 31
Locations ............................................................................................................................... 32
© 2000 Cisco Systems, Inc.
Cisco IP Telephony Troubleshooting Guide
for Cisco CallManager Release 3.0(1)
1

Advertisement

   Also See for Cisco 30 VIP

   Related Manuals for Cisco 30 VIP

   Summary of Contents for Cisco 30 VIP

  • Page 1: Table Of Contents

    One-Way Audio or No Audio ... 26 MTP and One-Way Audio ... 27 Phone Resets ... 27 Dropped Calls... 28 Check Your Loads... 31 Cisco CallManager Feature Issues ... 31 Codec/Regions: Codec Mismatch ... 31 Locations ... 32 © 2000 Cisco Systems, Inc.

  • Page 2

    Removing Records ... 78 Table Schema ... 78 Known Issues ... 79 IP to Device Name Translation ... 79 OnNet vs. OffNet ... 79 OffNet Digits Dialed ... 79 Fields in a Call Detail Record ... 79 © 2000 Cisco Systems, Inc.

  • Page 3

    Codec Types (Compression / Payload types)... 89 Cause Codes ... 89 Alarms ... 91 Unable to write CDR data. (Alarm # 1711 - Major Alarm)... 91 Calling Cisco Technical Assistance Center (TAC)... 92 Index... 93 © 2000 Cisco Systems, Inc.

  • Page 4: Purpose

    IP telephony system. When working with switched networks, knowing the state of the spanning-tree for redundancy is critical. The state of the network should be documented before any failure occurs. © 2000 Cisco Systems, Inc.

  • Page 5: Documentation Checklist

    Voice over IP (VoIP) traffic can be serviced with minimal delay and contention for resources. For additional information on this topic, see: http://www.cisco.com/warp/public/793/voip/ © 2000 Cisco Systems, Inc.

  • Page 6: Glossary Of Terms

    Cisco IOS Cluster codec D-Channel DHCP © 2000 Cisco Systems, Inc. Definition Configuration file used by devices. Companding technique commonly used in North America. µ-law is standardized as a 64-kbps codec in ITU-T G.711. ITU-T companding standard used in the conversion between analog and digital signals in PCM systems.

  • Page 7

    Route List. Private Branch Exchange. Digital or analog telephone switchboard located on the subscriber premises and used to connect private and public telephone networks. © 2000 Cisco Systems, Inc.

  • Page 8

    Structured Query Language. International standard language for defining and accessing relational databases. T1/CAS T1 is a digital WAN carrier facility, transmitting DS-1-formatted data at © 2000 Cisco Systems, Inc.

  • Page 9

    (using management software) so that they can communicate as if they were attached to the same wire, when in fact they are located on a number of different LAN segments. Because VLANs are based on logical instead of physical connections, they are extremely flexible. © 2000 Cisco Systems, Inc.

  • Page 10: Tools And Utilities To Monitor And Troubleshoot Cisco Callmanager

    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 more detailed explanation of Cisco CallManager Administration is available at the following location: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/index.htm © 2000 Cisco Systems, Inc.

  • Page 11: Microsoft Performance

    Choose the object, counter, and instance you want to include. Please refer to the Remote Serviceability documentation for instructions on how to use objects and counters to customize Microsoft Performance for Cisco CallManager operations. http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_0/service/index.htm © 2000 Cisco Systems, Inc. Add Counters Click the Add button. The Add...

  • Page 12: Microsoft Event Viewer

    To open the Event Log on the server PC running Cisco CallManager, click Start > Settings > Control Panel > Administrative Tools > Event Viewer. The Event Viewer provides error logs for System, Security, and Applications. Cisco CallManager errors are logged under the Application log. © 2000 Cisco Systems, Inc.

  • Page 13: Detailed Information About Events

    KeepAlive process, call flow, digit analysis, and related devices such as Cisco IP Phones, Gateways, Gatekeepers, and more. This information can help you isolate problems when troubleshooting Cisco CallManager. To properly track the information you © 2000 Cisco Systems, Inc.

  • Page 14: Configuring Traces

    Traces are composed of user mask flags (also known as bits) and trace levels. Open Cisco CallManager Administration. To turn on tracing, set your trace parameters (including configured service, bits, and so on) in the Service>Trace screen. Refer to the Cisco CallManager © 2000 Cisco Systems, Inc.

  • Page 15: 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.

  • Page 16

    Cisco CallManager Administration. Following are two examples of desired values based on the particular problem. The recommended value for normal call debugging is SdlTraceTypeFlags=0x00000b04 The recommended value for low level debugging or debugging gateways is SdlTraceTypeFlags=0x00004b05 © 2000 Cisco Systems, Inc.

  • Page 17: Disk Space Warning

    For this reason, we advise you to turn on the trace file for a specific amount of time, then review the information and turn off the trace. © 2000 Cisco Systems, Inc. Definition...

  • Page 18: Sniffer Trace

    Cisco CallManager when it fails before the calls terminate. Refer to the Appendix in the back of this book for detailed information about CDRs and CMRs. The information provided includes: Reading and Writing Records Known Issues List of record types generated © 2000 Cisco Systems, Inc. http://www.sniffer.com/ http://www.wwgsolutions.com/products/domino/domino.html...

  • Page 19: Enabling Or Disabling Cdrs

    1. Open Cisco CallManager Administration. 2. Select Service > Service Parameters. 3. Select the IP address of your Cisco CallManager installation. 4. From the list of Parameters, select CDREnabled. 5. Define type as boolean. 6. Select T for True. © 2000 Cisco Systems, Inc.

  • Page 20: Cdrs

    This level of detail can provide explanations for some problems, such as one-way audio. For example, a one-way audio problem is indicated if a packet size of 10,000 is sent, but the received size is only 10. © 2000 Cisco Systems, Inc.

  • Page 21: Problem Categories

    Cisco IP Phone 7960 can buffer as much as one second of voice samples. The jitter buffer is adaptive, meaning if a burst of packets is received, the Cisco IP Phone 7960 can play them out in an attempt to control the jitter. The network administrator needs to minimize the variation © 2000 Cisco Systems, Inc.

  • Page 22

    If a network analyzer is available, then a monitored call between two phones should have 50 packets per second (or 1 packet every 20 ms) when silence suppression is disabled. With proper filtering, it should be possible to identify if packets are being lost or delayed excessively. © 2000 Cisco Systems, Inc.

  • Page 23

    Cisco IOS Gateway, for example, we only see the diagnostic information from the Cisco IP Phone, not the gateway because there is no mechanism for it to notify the SQL database with this information. © 2000 Cisco Systems, Inc. Time – delta (ms)

  • Page 24: Button Help

    There is congestion in the WAN itself On the LAN, the most common problems are physical-level errors (such as CRC errors) caused by faulty cables, interfaces, or by incorrectly configured devices (such as a port speed or duplex © 2000 Cisco Systems, Inc.

  • Page 25: Crackling

    When troubleshooting echo problems, make sure that the phones that are being tested or examined are not using the speakerphone, and that they have the headset volume to reasonable © 2000 Cisco Systems, Inc. Voice Network Jane...

  • Page 26: Check Your Loads

    (such as access lists on a router) that may be blocking the audio in one or both directions. If the one-way audio occurs only through a voice- © 2000 Cisco Systems, Inc.

  • Page 27: Mtp And One-way Audio

    2. Check CCO (Cisco Connection Online at www.cisco.com) for the latest software loads, new patches, or release notes relating to the problem. 3. Check the Event Viewer for instances of phone(s) resetting. Phone resets are considered Information events, as shown in the following illustration. © 2000 Cisco Systems, Inc.

  • Page 28: Dropped Calls

    The first step is to determine if this problem is isolated to one phone or a group of phones. Perhaps the affected phones are all on a particular subnet or location. The next step is to check the Event Viewer for phone or gateway resets. © 2000 Cisco Systems, Inc.

  • Page 29

    Cisco CallManager resets the connection. This may be because a phone was turned off or there may be a problem in the network. If this is an intermittent problem, it may be useful to use Microsoft Performance to record phone registrations. © 2000 Cisco Systems, Inc.

  • Page 30

    Detail Records (CDR). The CDR files will give a Cause Of Termination (COT) that may help determine the cause of the problem. See the CDR section in the Problem Categories section above, or Appendix D for more information about CDRs. © 2000 Cisco Systems, Inc.

  • Page 31: Check Your Loads

    Note: The following codecs are supported for each device: Cisco IP Phone 7960 — G.711A-law/µ-law, G.729AnnexB Cisco IP Phone SP12 series and VIP 30 — G.711A-law/µ-law, G.723.1 Cisco Access Gateway DE30 and DT-24+ — G.711A-law/µ-law, G.723.1 © 2000 Cisco Systems, Inc.

  • Page 32: Locations

    11:14:05.390 Cisco CallManager|UnicastBridgeControl - wait_capabilities_StationCapRes - Device= CFB00107B000FB0 - Registered - ConfBridges= 5, Streams= 16, tcpHandle=4f19d64 11:14:05.480 Cisco CallManager|UnicastBridgeManager - UnicastBridgeRegistrationReq - Device Registration Complete for Name= Xoð´ ô%ð´ - DeviceType= 51, ResourcesAvailable= 5, deviceTblIndex= 0 © 2000 Cisco Systems, Inc.

  • Page 33: Transcoding Problems

    One E1 port (WS-X6608-E1 card contains 8x E1 ports) provides Transcoder/MTP resources for 16 calls, as shown in the following trace. 11:51:09.939 Cisco CallManager|MediaTerminationPointControl - Capabilities Received - Device= MTP00107B000FB1 - Registered - Supports 16 calls © 2000 Cisco Systems, Inc. Duplex Speed Type full - Conf Bridge...

  • Page 34

    In order to make a call between two devices using a low bit rate code (such as G.729 and G.723) that do not support the same codec, a transcoder resource is required. Consider the following illustration: Region1 © 2000 Cisco Systems, Inc. Duplex Speed Type full - MTP...

  • Page 35: Mtp Resource Problems

    MTP00107B000FB1 - Registered - Supports 16 calls The following hardware trace from the Cisco Catalyst 6000 8 Port Voice T1/E1 and Services Module, indicates that the E1 port 4/2 in the card has registered as an MTP/transcoder with Cisco CallManager. © 2000 Cisco Systems, Inc.

  • Page 36

    15:22:23.848 Cisco CallManager|MediaManager - wait_AllocateMtpResourceRes - start 2 connections 15:22:23.848 Cisco CallManager|MediaManager - wait_AllocateMtpResourceRes - creating connection between party1(16777357) and party2(16777359) 15:22:23.848 Cisco CallManager|MediaManager - wait_AllocateMtpResourceRes - creating connection between party1(16777358) and party2(16777359) © 2000 Cisco Systems, Inc. Duplex Speed Type full - MTP IP-Address...

  • Page 37: Dial Plans

    If it's a Route List, check which Route Groups are part of the list and which Gateway(s) is part of the Route Groups. Verify that the applicable devices are registered with Cisco CallManager. If there's no access to Cisco CallManager, get the "show tech" to capture this information and verify. © 2000 Cisco Systems, Inc.

  • Page 38: Partitions

    08:38:55.671 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 5 tcpHandle=0x6b88028 08:38:55.671 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x6b88028 08:38:55.671 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028 08:38:55.671 Cisco CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="5") 08:38:55.671 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist © 2000 Cisco Systems, Inc.

  • Page 39

    08:38:59.703 Cisco CallManager|StationD - stationOutputStartTone: 37=ReorderTone tcpHandle=0x6b88028 Route partitions work by associating a partition name with every directory number in the system. The directory number can be called only if the calling device contains the partition within a list © 2000 Cisco Systems, Inc.

  • Page 40: Security

    Route Pattern. Another way to get a handle on the dial plan is to go to the Route Plan Report page. Following is an option on the far right-hand side to "View In File". © 2000 Cisco Systems, Inc. Clause...

  • Page 41

    Filters or the Calling Search Spaces of the directory numbers. More information is available on the actual Route Plan Report. If you must contact the Cisco TAC, send this page via email if the Cisco CallManager is inaccessible. © 2000 Cisco Systems, Inc. Pattern Device Name...

  • Page 42: Slow Server Response

    3. Start an SDI trace and recreate the problem. Reorder tones could be the result of a configuration issue with location-based admission control or gatekeeper-based admission control where the Cisco CallManager might limit the number of allowable calls. In the SDI © 2000 Cisco Systems, Inc.

  • Page 43: Gateway Registration Problems

    If not, then either the gateway cannot contact the DHCP server (Is a router improperly configured and not forwarding DHCP broadcasts? Is the server running?), or © 2000 Cisco Systems, Inc.

  • Page 44

    00:00:06.570 (CFG) DHCP Server Response Processed, DHCPState = INIT_REBOOT 00:00:06.780 (CFG) IP Configuration Change! Restarting now... 00:00:10.480 (CFG) DHCP Request or Discovery Sent, DHCPState = INIT 00:00:14:480 (CFG) DHCP Timeout Waiting on Server, DHCPState = INIT © 2000 Cisco Systems, Inc.

  • Page 45

    NMP tells it for the TFTP server address, even if the NMP has DHCP disabled. You can check the current TFTP server IP address in a gateway by using the tracy utility. Enter the following command to get the configuration task number: TaskID: 0 Cmd: show tl © 2000 Cisco Systems, Inc.

  • Page 46

    00:00:05.370 (CFG) Requesting SAADefault.cnf File From TFTP Server 00:00:05.380 (CFG) .cnf File Received and Parsed Successfully. 00:00:05.380 (CFG) Updating Configuration ROM... 00:00:05.610 GMSG: GWEvent = CFG_DONE --> GWState = SrchActive 00:00:05.610 GMSG: CCM#0 CPEvent = CONNECT_REQ --> CPState = AttemptingSocket © 2000 Cisco Systems, Inc.

  • Page 47

    00:00:05.730 (CFG) DHCP Request or Discovery Sent, DHCPState = INIT_REBOOT 00:00:05.730 (CFG) DHCP Server Response Processed, DHCPState = BOUND 00:00:05.730 (CFG) Requesting DNS Resolution of CiscoCM1 00:00:05.730 (CFG) DNS Error on Resolving TFTP Server Name. © 2000 Cisco Systems, Inc. A0021300...

  • Page 48: Gatekeeper Problems

    2. Show gatekeeper status – verify the gatekeeper state is up. 3. Is there a zone subnet defined on the gatekeeper? If so, verify that the subnet of the gateway is in the allowed subnets. © 2000 Cisco Systems, Inc.

  • Page 49: Registration Rejects (rrj)

    2. Show gatekeeper status – verify the gatekeeper state is up. 3. Is there a zone subnet defined on the gatekeeper? If so, verify that the subnet of the gateway is in the allowed subnets. © 2000 Cisco Systems, Inc.

  • Page 50: Intra-cluster Cisco Ip Phone-to-cisco Ip Phone Calls

    2. If a DNS name of the TFTP sever is sent by DHCP, then a DNS sever IP address is required to map the name to an IP address. This step is bypassed if the DHCP server sends the IP © 2000 Cisco Systems, Inc.

  • Page 51

    The following Sniffer trace example summarizes the phone initialization process. This trace example is not taken for this case study’s sample topology, but it does provide an example of the series of events that occur during the Cisco IP Phone initialization process. © 2000 Cisco Systems, Inc.

  • Page 52: Skinny Station Registration Process

    Cisco CallManager of its existence and to make calling possible. The following figure shows the different messages that are exchanged between the Cisco IP Phone (the “station”) and the Cisco CallManager. Skinny Client Additional Optional Messages © 2000 Cisco Systems, Inc. StationRegister StationReset StationIpPort StationRegisterAck StationCapabilitiesReq...

  • Page 53: Cisco Ip Phone-to-cisco Ip Phone Call Flow Within A Cluster

    Skinny Station session (with TCP as the underlying protocol) with the Cisco CallManager. After call control signaling is established between the two Cisco IP Phones © 2000 Cisco Systems, Inc. Description The station sends this message to announce its existence to the controlling Cisco CallManager.

  • Page 54: Cisco Ip Phone-to-cisco Ip Phone Exchange Of Skinny Station Messages During Call Flow

    English so they can be readily understood by end-users. Because of this, these messages are not explained in this section. However, these call flow Skinny Station messages are explained in more detail in later sections when traces are being examined. © 2000 Cisco Systems, Inc.

  • Page 55: Cisco Callmanager Initialization Process

    Cisco CallManagers, in this case, CCM1. Review the descriptions of each message below. The first message indicates Cisco CallManager started its initialization process. © 2000 Cisco Systems, Inc. Station Call Info Station Set Lamp (Blink)

  • Page 56: Self-starting Processes

    Cluster 1 and considered an H.323 device. In this case, the RouteGroup is created to route calls to CCM3 in Cluster 1 with Cisco IOS Gatekeeper permission. If there is a problem © 2000 Cisco Systems, Inc. starting.

  • Page 57: Cisco Callmanager Registration Process

    16:02:52.750 CCM|StationInit - New connection accepted. DeviceName=, TCPHandle=0x4fe05e8, Socket=0x59c, IPAddr=172.16.70.228, Port=3280, StationD=[0,0,0] 16:02:52.781 CCM|StationInit - Processing StationReg. regCount: 1 DeviceName=MTP_nsa-cm1, TCPHandle=0x4fbaa00, Socket=0x594, IPAddr=172.16.70.228, Port=3279, StationD=[1,45,2] 16:02:52.781 CCM|StationInit - Processing StationReg. regCount: 1 DeviceName=CFB_nsa-cm1, TCPHandle=0x4fe05e8, Socket=0x59c, IPAddr=172.16.70.228, Port=3280, StationD=[1,96,2] © 2000 Cisco Systems, Inc.

  • Page 58: Cisco Callmanager Keepalive Process

    The messages in the following trace depict the KeepAlive sequence which indicates that the communications link between the Cisco CallManager and the station is active. Again, these messages can originate either by the Cisco CallManager or the station. © 2000 Cisco Systems, Inc.

  • Page 59: Cisco Callmanager Intra-cluster Call Flow Traces

    Station to select a specific set of soft keys. 16:05:41.625 CCM|StationD - stationOutputSelectSoftKeys tcpHandle=0x4fbbc30 The next message is used by Cisco CallManager to instruct the Skinny Station as to the correct line context for the display. 16:05:41.625 CCM|StationD - stationOutputActivateCallPlane tcpHandle=0x4fbbc30 © 2000 Cisco Systems, Inc.

  • Page 60

    Any extra digits pressed on the phone after this point will be ignored by Cisco CallManager, since a match has already been found. 16:05:43.562 CCM|Digit analysis: analysis results 16:05:43.562 CCM||PretransformCallingPartyNumber=1001 |CallingPartyNumber=1001 |DialingPattern=1000 |DialingRoutePatternRegularExpression=(1000) |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(1,38,2) |PretransformDigitString=1000 |PretransformPositionalMatchList=1000 |CollectedDigits=1000 |PositionalMatchList=1000 |RouteBlockFlag=RouteThisPattern © 2000 Cisco Systems, Inc.

  • Page 61

    (milliseconds). PacketSize is an integer containing the sampling time in milliseconds used to create the RTP packets. NOTE: normally this value is set to 30msec. In this case it is set to 20msec. © 2000 Cisco Systems, Inc.

  • Page 62

    The calling party’s Cisco IP Phone finally goes on-hook, which terminates all the control messages between the Skinny Station and Cisco CallManager as well as the RTP stream between Skinny Stations. 16:05:46.203 CCM|StationInit - InboundStim - OnHookMessageID tcpHandle=0x4fbbc30 © 2000 Cisco Systems, Inc.

  • Page 63: Cisco Ip Phone-to-cisco Ios Gateway Calls

    In this call flow, a Cisco IP Phone (directory number 1001) located in the cluster 2 is calling a phone (directory number 3333) located somewhere on the PSTN. Remember that you can follow a device through the trace by looking at the TCP handle value, time stamp, or name of the © 2000 Cisco Systems, Inc.

  • Page 64

    The following traces show the calling and called party information. In this example, the calling party name and number is the same because the administrator has not configured a display name, such as “John Smith.” © 2000 Cisco Systems, Inc.

  • Page 65

    When the H.225 connect message is received, the call has been connected. 15:20:22.968 CCM|In Message -- H225ConnectMsg -- Protocol= H225Protocol 15:20:22.968 CCM|StationD - stationOutputCallInfo CallingPartyName=1001, CallingParty=1001, CalledPartyName=, CalledParty=3333, tcpHandle=0x5138d98 15:20:22.062 CCM|MediaCoordinator - wait_AuConnectInfoInd © 2000 Cisco Systems, Inc.

  • Page 66: Debug Messages And Show Commands On The Cisco Ios Gatekeeper

    (DRQ) from the Cisco CallManager (172.16.70.228), and the Cisco IOS Gatekeeper has sent a disengage confirmed (DCF) to the Cisco CallManager. *Mar 12 04:03:57.181: RASLibRASRecvData DRQ (seq# 3366) rcvd from [172.16.70.228883] on sock [0x60AF038C] © 2000 Cisco Systems, Inc.

  • Page 67: Debug Messages And Show Commands On The Cisco Ios Gateway

    H.323 version being used. The following debug shows that H.323 version 2 is being used. The called and calling party numbers are also shown. - Source Address H323-ID - Destination Address e164 © 2000 Cisco Systems, Inc. Type ---- 1493 gka.cisco.com VOIP-GW 3923 gka.cisco.com...

  • Page 68

    The following debug output shows the H.225 Alerting messages are returning to the Cisco CallManager. *Mar 12 04:03:57.197: ccCallSetContext (callID=0x12, context=0x61466B30) *Mar 12 04:03:57.197: ccCallProceeding (callID=0x11, prog_ind=0x0) *Mar 12 04:03:57.197: cc_api_call_proceeding(vdbPtr=0x617BE064, callID=0x12, prog_ind=0x0) *Mar 12 04:03:57.197: cc_api_call_alert(vdbPtr=0x617BE064, callID=0x12, prog_ind=0x8, sig_ind=0x1) © 2000 Cisco Systems, Inc.

  • Page 69

    *Mar 12 04:03:57.217: ssa: cid(17)st(3)oldst(0)cfid(7)csize(0)in(1)fDest(1)-cid2(18)st2(3)oldst2(1) *Mar 12 04:03:57.653: cc_api_caps_ind (dstVdbPtr=0x617BE064, dstCallId=0x12, srcCallId=0x11, caps={codec=0x1, fax_rate=0x2, vad=0x2, modem=0x1, codec_bytes=160, signal_type=0}) The following debug output shows that both parties negotiated correctly and agreed on G.711 codec with 160 bytes of data. © 2000 Cisco Systems, Inc.

  • Page 70: Cisco Ios Gateway With T1/pri Interface

    If it were a 0x8890218F, then it would be a 56kb/s data call and 0x8090A3 if it is a voice call. In the debug output below, the bearer capability is 0x8090A3, which is for voice. Called and calling party numbers are also shown. © 2000 Cisco Systems, Inc.

  • Page 71: Cisco Ios Gateway With T1/cas Interface

    Apr 5 17:58:21.859: from NEAT(0): (0/15): Rx LOOP_CLOSURE (ABCD=1111) Apr 5 17:58:22.083: from NEAT(0): (0/15): Rx LOOP_OPEN (ABCD=0000) The following debug message indicates the Cisco IOS Gateway is going off-hook. Apr 5 17:58:23.499: from NEAT(0): (0/15): Rx LOOP_CLOSURE (ABCD=1111) © 2000 Cisco Systems, Inc.

  • Page 72

    511D : 156043737hs.1 +645 pid:0 Answer 1001 active tx:1752/280320 rx:988/158080 IP172.16.70.228:18888 rtt:0ms pl:15750/80ms lost:0/0/0 delay:25/25/65ms g711ulaw 511D : 156043738hs.1 +644 pid:1 Originate 3333 active tx:988/136972 rx:1759/302548 Tele 1/0/0 (30): tx:39090/35195/0ms g711ulaw noise:-43 acom:0 i/0:-36/-42 dBm © 2000 Cisco Systems, Inc.

  • Page 73: Inter-cluster Cisco Ip Phone-to-cisco Ip Phone Calls

    Cisco CallManager via Skinny Station protocol, and the Cisco CallManager can talk with the Cisco IOS Gatekeeper using the H.323 RAS protocol. The Admission Request message (ARQ) is sent to the Cisco IOS Gatekeeper, which sends the Admission Confirmed message (ACF) after © 2000 Cisco Systems, Inc.

  • Page 74: Call Flow Traces

    TCP handle, and the calling number, which is displayed on the Cisco IP Phone. The called number (1001), H.225 connect, and H.245 confirm messages can be seen in the following debug output. The codec type is G.711 µ-law. © 2000 Cisco Systems, Inc.

  • Page 75: Failed Call Flow

    In the traces below, the Cisco IP Phone (1001) has gone off-hook. A TCP handle is assigned to the Cisco IP Phone. 16:05:33.468 CCM|StationInit - InboundStim - OffHookMessageID tcpHandle=0x4fbbc30 16:05:33.468 CCM|StationD - stationOutputDisplayText tcpHandle=0x4fbbc30, Display= 1001 © 2000 Cisco Systems, Inc.

  • Page 76

    (1001), which is followed by an on-hook message. 16:05:36.812 CCM|Digit analysis: analysis results 16:05:36.812 CCM||PretransformCallingPartyNumber=1001 |CallingPartyNumber=1001 |DialingPattern=2XXX |DialingRoutePatternRegularExpression=(2XXX) |PotentialMatches=NoPotentialMatchesExist |CollectedDigits=2000 16:05:36.828 CCM|StationD - stationOutputCallInfo CallingPartyName=1001, CallingParty=1001, CalledPartyName=, CalledParty=2000, tcpHandle=0x4fbbc30 16:05:36.828 CCM|StationD - stationOutputStartTone: 37=ReorderTone tcpHandle=0x4fbbc30 16:05:37.953 CCM|StationInit - InboundStim - OnHookMessageID tcpHandle=0x4fbbc30 © 2000 Cisco Systems, Inc.

  • Page 77: Call Detail Records (cdrs And Cmrs)

    The names will differ by adding one to the number of the name. For instance, the original name is CCM0300. After a migration, the newer database name will be CCM0301. The highest number database should be used. © 2000 Cisco Systems, Inc.

  • Page 78: Removing Records

    The CallDetailRecord table holds information about the endpoints of the call and other call control/routing aspects of the call. The CallDetailRecordDiagnostic table holds information about the quality of the streamed audio of the call. © 2000 Cisco Systems, Inc. Systems Inc.\DBL” for the item called SQl UserID...

  • Page 79: Known Issues

    This field is a time_t value that is obtained from the Windows NT (2000) system routines. The value is a coordinated universal time (UTC) value, and represents the number of seconds since Midnight (00:00:00) Jan. 1, 1970. © 2000 Cisco Systems, Inc.

  • Page 80: Deciphering The Time Stamp

    This converts to a Hex value of 0x3B12A8C0 Reverse Byte order = C0A8123B Bytes Converted from Hex to Decimal = 192 168 18 59 which would be displayed as 192.168.18.59. © 2000 Cisco Systems, Inc. CO A8 12 BC C0 A8 12 3B...

  • Page 81: Cdr Field Definition

    © 2000 Cisco Systems, Inc. Definition Type of this record unsigned integer Specifies the type of this specific record. It could be a Start call record(0), End call record(1), or a CMR record(2). Global Call Identifier The Global Call Identifier consists of two fields which are both unsigned integers.

  • Page 82

    © 2000 Cisco Systems, Inc. Calling party’s partition up to 50 characters This field contains the Partition associated with the calling party. ISDN location value unsigned integer This field contains the location value from the Cause information Element.

  • Page 83

    © 2000 Cisco Systems, Inc. The node identifier for the node where the destination of the call was registered unsigned integer The node within the Cisco CallManager cluster where the destination device was registered at the time of this call.

  • Page 84

    © 2000 Cisco Systems, Inc. Called party cause of call termination unsigned integer This cause represents why the call to the termination device was terminated. In the case of transfers, forwards, and so on, the cause of call termination may be different for the recipient of the call and the originator of the call.

  • Page 85: Cmr Field Definitions

    © 2000 Cisco Systems, Inc. Definition Type of this record unsigned integer Specifies the type of this specific record. It will be set to CMR record. Global Call Identifier for this call The Global Call Identifier consists of two fields which are both unsigned integers.

  • Page 86: Call Records Logged By Call Type

    CMR records written: one for the originator, and one for the destination of the call. This section describes the records written for different call types in the system. © 2000 Cisco Systems, Inc. The number of octets (bytes) of data received during this...

  • Page 87: Normal Calls (cisco Ip Phone-to-cisco Ip Phone)

    Called Party IP and Date/Time Connect fields will be blank. If the originator abandoned the call, the cause will be “NO_ERROR” (0). The Duration will always be zero seconds. These calls will not be logged unless “CdrLogCallsWithZeroDurationFlag” is enabled. © 2000 Cisco Systems, Inc.

  • Page 88: Call Management Records Logged By Call Type

    If the calls are logged, they will be logged as normal calls with all relevant fields containing data. There will only be one record per call since the calls were never connected to a destination. The record will be for the originator of the call. © 2000 Cisco Systems, Inc.

  • Page 89: Codec Types (compression / Payload Types)

    Channel unacceptable Call awarded and being delivered in an established channel Preemption Preemption - circuit reserved for reuse Normal call clearing User busy No user responding No answer from user (user alerted) Subscriber absent Call rejected © 2000 Cisco Systems, Inc.

  • Page 90

    The message is not compatible with the call state The call was terminated when a timer expired and a recovery routine was executed to recover from the error Parameter non-existent or not implemented - passed on (national use) Message with unrecognized parameter discarded © 2000 Cisco Systems, Inc.

  • Page 91: Alarms

    Cisco CallManager does not have sufficient privileges to open the file for writing to the database. Make sure Cisco CallManager has privileges that will permit write operations. The path is not set up, or the database server is down. © 2000 Cisco Systems, Inc.

  • Page 92: Calling Cisco Technical Assistance Center (tac)

    If the problem is with calls through a Cisco IOS Gateway, please also provide: o “debug voice ccapi inout” o “debug isdn q931” o [AS5300 only] “sh vfc xboard” o [AS5300 only] “sh vfc x version dspware” o [AS5300 only] “sh vfc x version vcware” © 2000 Cisco Systems, Inc.

  • Page 93: Index

    IP addresses ... 80 Known issues ... 79 Normal calls (logging) ... 87 Note about clustering ... 20 Payload types ... 89 © 2000 Cisco Systems, Inc. Index Reading records... 77 Records logged by call type ... 86 Removing records ... 78 Table schema...

  • Page 94

    Cisco IOS Gatekeeper ... 66 Cisco IOS Gateway ... 67 Details Cisco CallManager Administration... 10 DHCP (definition) ... 6 © 2000 Cisco Systems, Inc. Diagnostic CDRs... See Call Management Records (CMR) Dial Plan... 37 Distorted Audio Problem ... 21 DN (definition)... 6 DNIS (definition) ...

  • Page 95

    Resource problem... 35 MGCP (definition) ... 7 MTP (definition) ... 7 Network Analyzer ... 18 No Audio ... 26 © 2000 Cisco Systems, Inc. One-Way Audio ... 26 and Media Termination Point... 27 Partition (definition)... 7 Partitions... 38 Payload Types CDRs ...

  • Page 96

    Cisco IOS Gateway ... 67 Show-tech Example... 40 Output... 41 Silence Suppression (definition) ... 8 © 2000 Cisco Systems, Inc. Skinny Station Cisco IP Phone-to-Cisco IP Phone message exchange ... 54 Registration process ... 52 Registration process definitions ... 53 Sniffer Trace...

This manual also for:

30

Comments to this Manuals

Symbols: 0
Latest comments: