[cisco-voip] troubleshooting IP phone 7960 keepalives

[Wes Sisk]

KA Acks were removed from traces long ago.

the more important message to look for is the ALARM message the phone 
sends to the failover server (or the next server it tries to register 
to, in the case it re-registers back to the same server)

use this:
cd prog*\cisco\trace\ccm
findstr Last= ccm*.txt >l.txt
notepad l.txt

This Last= is the phone's point of view on why it lost registration with 
the last CM server.  Should be one of these values:
0    Phone Load Is Rejected
1    Phone Load TFTP Size Error
2    Phone Load Compressor Error
3    Phone Load Version Error
4    Disk Full Error
5    Checksum Error
6    Phone Load Not Found in TFTP Server
7    TFTP Timeout
8    TFTP Access Error
9    TFTP Error
10    CCM TCP Connection timeout
11    CCM TCP Connection Close because of bad Ack
12    CCM Resets TCP Connection
13    CCM Aborts TCP Connection
14    CCM TCP Connection Closed
15    CCM TCP Connection Closed because ICMP Unreachable
16    CCM Rejects TCP Connection
17    Keepalive Time Out
18    Fail Back to Primary CCM
20    User Resets Phone By Keypad
21    Phone Resets because IP configuration
22    CCM Resets Phone
23    CCM Restarts Phone
24    CCM Rejects Phone Registration
25    Phone Initializes
26    CCM TCP Connection Closed With Unknown Reason
27    Waiting For State From CCM
28    Waiting For Response From CCM
29    DSP Alarm
30    Phone Abort CCM TCP Connection
31    File Authorization Failed

/Wes



Justin Steinberg wrote:

>I have some phones that periodically reset themselves at random times
>during the day, I even have some instances when the phone reset itself
>while on an active call.
>
>When I look at a detailed callmanager trace i see the following entries:
>
>11/15/2005 15:21:29.108 CCM|StationInit - Keep alive timeout.:
>000000741|<CLID::xxxCMPUB01-Cluster><NID::10.xxx.xxx.xxx><CT::2,100,90,1.1122347><IP::10.xxx.xxx.xxx><DEV::SEP000C853Bxxxx>
>11/15/2005 15:21:29.108 CCM|StationInit - Closing Station connection
>DeviceName=SEP000C853Bxxxx, TCPHandle=000000741,
>IPAddr=10.xxx.xxx.xxx, Port=52056, Device
>Controller=[2,89,737]|<CLID::xxxCMPUB01-Cluster><NID::10.xxx.xxx.xxx><CT::2,100,90,1.1122347><IP::10.xxx.xxx.xxx><DEV::SEP000C853Bxxx>
>11/15/2005 15:21:29.108 CCM|DeviceUnregistered - Device unregistered.
>Device name.:SEP000C853Bxxx Device IP address.:10.xxx.xxx.xxx Device
>type. [Optional]:7 Device description [Optional].:John Johnson 1128
>Reason Code [Optional].:8 App ID:Cisco CallManager Cluster
>ID:xxxCMPUB01-Cluster Node
>
>
>It seems like the phone is reporting to the CallManager that it is not
>receiving keepalives and so the phone reboots.  I noticed that
>detailed callmanager traces log the incoming keepalives that the
>phones send to CallManager.  But I do not see the callManagers
>KeepAliveAcks in the detailed CCM trace log.  Do I have to run a
>packet capture to see this?
>
>Also, the phones and CallManager are on the same lan - so latency/loss
>SHOULD not be an issue.
>
>TIA
>
>justin
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>  
>