Appendix B Case Study: Troubleshooting Cisco Unified IP Phone Calls
Troubleshooting Intercluster Cisco Unified IP Phone Calls
In this call flow, a Cisco Unified IP Phone (2002) located in Cluster 2 is calling a
Cisco Unified IP Phone (1001) located in Cluster 1. 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.
In the following traces, the Cisco Unified IP Phone (2002) has gone off hook. The trace shows the unique messages, TCP handle, and the calling number, which displays on the Cisco Unified IP Phone. The following debug output shows the called number (1001), H.225 connect, and H.245 confirm messages. The codec type is G.711
16:06:13.921 CCMStationInit - InboundStim - OffHookMessageID tcpHandle=0x1c64310 16:06:13.953 CCMOut Message
16:06:13.953 CCMStationD - stationOutputCallInfo CallingPartyName=, CallingParty=2002, CalledPartyName=1001, CalledParty=1001, tcpHandle=0x1c64310
16:06:14.015 CCMH245Interface(2) OLC indication chan number = 2
16:06:14.015 CCMStationD - stationOutputOpenReceiveChannel tcpHandle=0x1c64310 myIP: e74610ac (172.16.70.231)
16:06:14.015 CCMStationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k
16:06:14.062 CCMStationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x1c64310, Status=0, IpAddr=0xe74610ac, Port=20444, PartyID=2 16:06:14.062 CCMH245Interface(2) paths established ip = e74610ac, port = 20444 16:06:14.187 CCMH245Interface(2) OLC outgoing confirm ip = fc4610ac, port = 29626
The following traces show the calling and called party number, which associates with an IP address and a hexidecimal value.
16:06:14.187 CCMStationD - stationOutputStartMediaTransmission tcpHandle=0x1c64310 myIP: e74610ac (172.16.70.231)
16:06:14.187 CCMStationD - RemoteIpAddr: fc4610ac (172.16.70.252)
The following traces show the packet sizes and the MAC address of the Cisco IP Phone (2002). The disconnect, then
RemoteRtpPortNumber: 29626 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k
16:06:16.515 | CCM Device SEP003094C26105 , UnRegisters with SDL Link to monitor NodeID= 1 |
16:06:16.515 | CCMStationD - stationOutputCloseReceiveChannel tcpHandle=0x1c64310 myIP: |
e74610ac (172.16.70.231) | |
16:06:16.515 | CCMStationD - stationOutputStopMediaTransmission tcpHandle=0x1c64310 myIP: |
e74610ac (172.16.70.231) | |
16:06:16.531 | CCMIn Message |
16:06:16.531 | CCMIe - Q931CauseIe |
16:06:16.531 | CCMIe - H225UserUserIe |
16:06:16.531 | CCMLocations:Orig=1 BW=64Dest=0 |
16:06:16.531 | CCMMediaManager - wait_AuDisconnectRequest - StopSession sending disconnect |
to (64,2) and remove connection from list | |
16:06:16.531 | CCMMediaManager - wait_AuDisconnectReply - received all disconnect replies, |
forwarding a | reply for party1(16777219) and party2(16777220) |
16:06:16.531 CCMMediaCoordinator - wait_AuDisconnectReply - removing MediaManager(2) from connection list
16:06:16.734 CCMStationInit - InboundStim - OnHookMessageID tcpHandle=0x1c64310
Failed Call Flow
The following section describes an unsuccessful intercluster call flow, as seen in the SDI trace. In the following traces, the Cisco Unified IP Phone (1001) goes off hook. A TCP handle gets assigned to the Cisco Unified IP Phone.
16:05:33.468 CCMStationInit - InboundStim - OffHookMessageID tcpHandle=0x4fbbc30 16:05:33.468 CCMStationD - stationOutputDisplayText tcpHandle=0x4fbbc30, Display= 1001
Troubleshooting Guide for Cisco Unified CallManager Release 5.0(2)
|
| ||
|
|
