Cisco Systems 30 VIP manual Cisco CallManager Intra-Cluster Call Flow Traces

Page 59

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

16:03:02.328 CCMMediaTerminationPointControl - stationOutputKeepAliveAck tcpHandle=4fa7dc0 16:03:02.328 CCMUnicastBridgeControl - stationOutputKeepAliveAck tcpHandle=4bf8a70 16:03:06.703 CCMStationInit - InboundStim - IpPortMessageID: 32715(0x7fcb) tcpHandle=0x4fbbc30 16:03:06.703 CCMStationD - stationOutputKeepAliveAck tcpHandle=0x4fbbc30

Cisco CallManager Intra-Cluster Call Flow Traces

The following SDI traces explore in detail the intra-cluster call flow. The Cisco IP Phones in the call flow can be identified by the directory number (dn), tcpHandle, and IP address. A

Cisco IP Phone (dn: 1001, tcpHandle: 0x4fbbc30, IP address: 172.16.70.231) located in Cluster 2 is calling another Cisco IP Phone in the same Cluster (dn=1000, tcpHandle= 0x4fbb150, IP address= 172.16.70.230). Remember that you can follow a device through the trace by looking at the TCP handle value, time stamp, or name of the device. The TCP handle value for the device remains the same until the device is rebooted or goes offline.

The following traces show that the Cisco IP Phone (1001) has gone off-hook. The trace below shows the unique messages, TCP handle, and the called number, which are displayed on the Cisco IP Phone. There is no calling number at this point, because the user has not tried to dial any digits. The information below is in the form of Skinny Station messages between the Cisco IP Phones and the Cisco CallManager.

16:05:41.625 CCMStationInit - InboundStim - OffHookMessageID tcpHandle=0x4fbbc30 16:05:41.625 CCMStationD - stationOutputDisplayText tcpHandle=0x4fbbc30, Display= 1001

The next trace shows Skinny Station messages going from Cisco CallManager to a

Cisco IP Phone. The first message is to turn on the lamp on the calling party’s Cisco IP Phone.

16:05:41.625 CCMStationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x4fbbc30

The stationOutputCallState message is used by Cisco CallManager to notify the station of certain call related information.

16:05:41.625 CCMStationD - stationOutputCallState tcpHandle=0x4fbbc30

The stationOutputDisplayPromptStatus message is used by Cisco CallManager to cause a call- related prompt message to be displayed on the Cisco IP Phone.

16:05:41.625 CCMStationD - stationOutputDisplayPromptStatus tcpHandle=0x4fbbc30

The stationOutputSelectSoftKey message is used by Cisco CallManager to cause the Skinny Station to select a specific set of soft keys.

16:05:41.625 CCMStationD - 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 CCMStationD - stationOutputActivateCallPlane tcpHandle=0x4fbbc30

© 2000 Cisco Systems, Inc.

59

Page 58 Page 60
Image 59
Page 58 Page 60
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 ClusterPartition Flow Full duplex 711 729 225 245 323 Half Duplex HookflashJitter Law mu-law Silence Suppression Voice Activation Detection 931Route Filter Route Group Route List Route Pattern Voice Activation Detection Silence Suppression VoIP Translation PatternCisco CallManager Administration Details View Report Microsoft PerformanceMicrosoft 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 IdentifierLatency experienced during this connection Lost RTP packets during this connectionInterarrival jitter 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
Top Page Image Contents