Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
© 2000 Cisco Systems, Inc.
61
The next trace shows that Cisco CallManager is sending out this information to a called party
phone (the phone is identified by the tcpHandle number).
16:05:43.578 CCM|StationD - stationOutputCallInfo CallingPartyName=1001, CallingParty=1001,
CalledPartyName=1000, CalledParty=1000, tcpHandle=0x4fbb150
The next trace indicates that Cisco CallManager is ordering the lamp to blink for incoming call
indication on the called party’s Cisco IP Phone.
16:05:43.578 CCM|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampBlink
tcpHandle=0x4fbb150
In the following traces, Cisco CallManager is providing ringer, display notification, and other
call-related information to the called party’s Cisco IP Phone. Again, you can see that all
messages are directed to the same Cisco IP Phone because the same tcpHandle is used
throughout the traces.
16:05:43.578 CCM|StationD - stationOutputSetRinger: 2=InsideRing tcpHandle=0x4fbb150
16:05:43.578 CCM|StationD - stationOutputDisplayNotify tcpHandle=0x4fbb150
16:05:43.578 CCM|StationD - stationOutputDisplayPromptStatus tcpHandle=0x4fbb150
16:05:43.578 CCM|StationD - stationOutputSelectSoftKeys tcpHandle=0x4fbb150
Notice that Cisco CallManager is also providing similar information to the calling party’s
Cisco IP Phone. Again, the tcpHandle is used to differentiate between Cisco IP Phones.
16:05:43.578 CCM|StationD - stationOutputCallInfo CallingPartyName=1001, CallingParty=1001,
CalledPartyName=, CalledParty=1000, tcpHandle=0x4fbbc30
16:05:43.578 CCM|StationD - stationOutputCallInfo CallingPartyName=1001, CallingParty=1001,
CalledPartyName=1000, CalledParty=1000, tcpHandle=0x4fbbc30
In the next trace, Cisco CallManager provides an alerting or ringing tone to the calling party’s
Cisco IP Phone, notifying that the connection has been established.
16:05:43.578 CCM|StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x4fbbc30
16:05:43.578 CCM|StationD - stationOutputCallState tcpHandle=0x4fbbc30
16:05:43.578 CCM|StationD - stationOutputSelectSoftKeys tcpHandle=0x4fbbc30
16:05:43.578 CCM|StationD - stationOutputDisplayPromptStatus tcpHandle=0x4fbbc30
At this point, the called party’s Cisco IP Phone goes off-hook. Therefore, Cisco CallManager
stops generating the ringer tone to calling party.
16:05:45.140 CCM|StationD - stationOutputStopTone tcpHandle=0x4fbbc30
In the following messages, Cisco CallManager causes the Skinny Station to begin receiving a
Unicast RTP stream. To do so, Cisco CallManager provides the IP address of the called party as
well as codec information, and packet size in msec (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.
