Cisco Systems OL-9420-01 appendix Cisco Unified CallManager KeepAlive Process

Page 5

Appendix B Case Study: Troubleshooting Cisco Unified IP Phone Calls

Troubleshooting Intracluster Cisco Unified IP Phone Calls

In the following trace, Cisco Unified CallManager has received new connections for registration. The registering devices are MTP_nsa-cm1 (MTP services on Unified CM1), and CFB_nsa-cm1 (Conference Bridge service on Unified CM1). Although these are software services that are running on

Cisco Unified CallManager, they get treated internally as different external services and therefore get assigned a TCPHandle, socket number, and port number as well as a device name.

16:02:52.750 CCMStationInit - New connection accepted. DeviceName=, TCPHandle=0x4fbaa00, Socket=0x594, IPAddr=172.16.70.228, Port=3279, StationD=[0,0,0]

16:02:52.750 CCMStationInit - New connection accepted. DeviceName=, TCPHandle=0x4fe05e8, Socket=0x59c, IPAddr=172.16.70.228, Port=3280, StationD=[0,0,0]

16:02:52.781 CCMStationInit - 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 CCMStationInit - Processing StationReg. regCount: 1 DeviceName=CFB_nsa-cm1, TCPHandle=0x4fe05e8, Socket=0x59c, IPAddr=172.16.70.228, Port=3280, StationD=[1,96,2]

Cisco Unified CallManager KeepAlive Process

The station, device, or service and the Cisco Unified CallManager use the following messages to maintain a knowledge of the communications channel between them. The messages begin the KeepAlive sequence that ensures that the communications link between the Cisco Unified CallManager and the station remains active. The following messages can originate from either the Cisco Unified CallManager or the station.

16:03:02.328 CCMStationInit - InboundStim - KeepAliveMessage - Forward KeepAlive to StationD. DeviceName=MTP_nsa-cm2, TCPHandle=0x4fa7dc0, Socket=0x568, IPAddr=172.16.70.229, Port=1556, StationD=[1,45,1]

16:03:02.328 CCMStationInit - InboundStim - KeepAliveMessage - Forward KeepAlive to StationD. DeviceName=CFB_nsa-cm2, TCPHandle=0x4bf8a70, Socket=0x57c, IPAddr=172.16.70.229, Port=1557, StationD=[1,96,1]

16:03:06.640 CCMStationInit - InboundStim - KeepAliveMessage - Forward KeepAlive to StationD. DeviceName=SEP0010EB001720, TCPHandle=0x4fbb150, Socket=0x600, IPAddr=172.16.70.230, Port=49211, StationD=[1,85,2]

16:03:06.703 CCMStationInit - InboundStim - KeepAliveMessage - Forward KeepAlive to StationD. DeviceName=SEP003094C26105, TCPHandle=0x4fbbc30, Socket=0x5a4, IPAddr=172.16.70.231, Port=52095, StationD=[1,85,1]

The messages in the following trace depict the KeepAlive sequence that indicates that the communications link between the Cisco Unified CallManager and the station is active. Again, these messages can originate from either the Cisco Unified CallManager or the station.

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 Unified CallManager Intracluster Call Flow Traces

The following SDI traces explore the intracluster call flow in detail. You can identify

Cisco Unified IP Phones in the call flow by the directory number (dn), tcpHandle, and IP address. A Cisco Unified IP Phone (dn: 1001, tcpHandle: 0x4fbbc30, IP address: 172.16.70.231) located in Cluster 2 is calling another Cisco Unified 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.

Troubleshooting Guide for Cisco Unified CallManager Release 5.0(2)

 

OL-9420-01

B-5

 

Image 5
Contents Sample Topology Case Study Troubleshooting Cisco Unified IP Phone CallsCisco Unified IP Phone Initialization Process ProcedureSelf-Starting Processes Cisco Unified CallManager Initialization ProcessCisco Unified CallManager Registration Process Cisco Unified CallManager Intracluster Call Flow Traces Cisco Unified CallManager KeepAlive ProcessCCMStationD stationOutputCallState tcpHandle=0x4fbbc30 Page CCMStationD stationOutputStopTone tcpHandle=0x4fbbc30 Call Flow Traces Intercluster H.323 CommunicationCCMIe H225UserUserIe -- IEData= 7E 00 1D 05 05 80 Failed Call FlowPage OL-9420-01