Cisco Systems 30 VIP

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

00:00:05.730 (CFG) TFTP Server IP Set by DHCP Option 150 = 10.123.9.2

00:00:05.730 (CFG) Requesting SAA00107B0013DE.cnf File From TFTP Server

00:00:05.730 (CFG) .cnf File Received and Parsed Successfully.

00:00:05.730 GMSG: GWEvent = CFG_DONE --> GWState = SrchActive

00:00:05.730 GMSG: CCM#0 CPEvent = CONNECT_REQ --> CPState = AttemptingSocket

00:00:05.730 GMSG: Attempting TCP socket with CCM 10.123.9.2

00:00:05.730 GMSG: CCM#0 CPEvent = SOCKET_ACK --> CPState = BackupCCM

00:00:05.730 GMSG: GWEvent = SOCKET_ACK --> GWState = RegActive

00:00:05.730 GMSG: CCM#0 CPEvent = REGISTER_REQ --> CPState = SentRegister

00:00:06.320 GMSG: CCM#0 CPEvent = LOADID --> CPState = LoadResponse

00:01:36.300 GMSG: CCM#0 CPEvent = TIMEOUT --> CPState = BadCCM

00:01:36.300 GMSG: GWEvent = DISCONNECT --> GWState = Rollover

00:01:46.870 GMSG: CCM#0 CPEvent = CLOSED --> CPState = NoTCPSocket

00:01:51.300 GMSG: GWEvent = TIMEOUT --> GWState = SrchActive

00:01:51.300 GMSG: CCM#0 CPEvent = CONNECT_REQ --> CPState = AttemptingSocket

00:01:51.300 GMSG: Attempting TCP socket with CCM 10.123.9.2

00:01:51.300 GMSG: CCM#0 CPEvent = SOCKET_ACK --> CPState = BackupCCM

00:01:51.300 GMSG: GWEvent = SOCKET_ACK --> GWState = RegActive

00:01:51.300 GMSG: CCM#0 CPEvent = REGISTER_REQ --> CPState = SentRegister

00:01:51.890 GMSG: CCM#0 CPEvent = LOADID --> CPState = LoadResponse

The difference here is that the gateway gets stuck in the ‘LoadResponse’ stage and eventually

times out. This problem can be resolved by correcting the load file name in the Device Defaults

area of Cisco CallManager Administration.

Gatekeeper Problems

Before starting any gateway-to-gatekeeper troubleshooting, verify that there is IP connectivity

within the network. Assuming that there is IP connectivity, use the information in this section to

troubleshoot your gateway.

Inter-Cluster Trunks Only

Note that gatekeeper control for Cisco CallManager Release 3.0(1) is only available for inter-

cluster trunks. Gatekeeper control is configurable for other devices, but the configuration is not

supported.

Admission Rejects (ARJ)

ARJs are issued when Cisco CallManager has registered with the Gatekeeper, but can’t send a

phone call. Configuration issues on the gatekeeper should be the primary focus when the

gatekeeper is issuing a ARJ. However, here are the general guidelines for troubleshooting:

1. Verify IP connectivity from the gateway to the gatekeeper.

2. Show gatekeeper status – verify the gatekeeper state is up.

3. Is there a zone subnet defined on the gatekeeper? If so, verify that the subnet of the gateway

is in the allowed subnets.