Filter
Top Products
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
© 2000 Cisco Systems, Inc. 67
*Mar 12 04:03:57.181: RASlibras_sendto msg length 3 from 172.16.70.2251719 to 172.16.70.228883
*Mar 12 04:03:57.181: RASLibRASSendDCF DCF (seq# 3366) sent to 172.16.70.228
*Mar 12 04:03:57.181: RASLibRASRecvData successfully rcvd message of length 124 from
172.16.70.228883
The command “show gatekeeper endpoints” on the Cisco IOS Gatekeeper shows that all four
Cisco CallManagers are registered with the Cisco IOS Gatekeeper. Remember that in the
topology for this case study, there are four Cisco CallManagers, two in each cluster. This
Cisco IOS Gatekeeper has two zones and each zone has two Cisco CallManagers.
R2514-1#show gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
===================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type
--------------- ----- --------------- ----- --------- ---- --
172.16.70.228 2 172.16.70.228 1493 gka.cisco.com VOIP-GW
H323-ID: ac1046e4->ac1046f5
172.16.70.229 2 172.16.70.229 3923 gka.cisco.com VOIP-GW
H323-ID: ac1046e5->ac1046f5
172.16.70.245 1 172.16.70.245 1041 gkb.cisco.com VOIP-GW
H323-ID: ac1046f5->ac1046e4
172.16.70.243 1 172.16.70.243 2043 gkb.cisco.com VOIP-GW
H323-ID: ac1046f5->ac1046e4
Total number of active registrations = 4
Debug Messages and Show Commands on the Cisco IOS Gateway
In the previous section, the Cisco IOS Gatekeeper show commands and debug outputs were
discussed in detail. This section focuses on the debug output and show commands on the
Cisco IOS Gateway. In the topology for this case study, calls are going through the
Cisco IOS Gateways. The Cisco IOS Gateway interfaces to the PSTN or PBX with either
T1/CAS or T1/PRI interfaces. Debug output of commands such as debug voip ccapi inout, debug
h225 events and debug h225 asn1, are shown below.
In the following debug output, the Cisco IOS Gateway is accepting the TCP connection request
from Cisco CallManager (172.16.70.228) on port 2328 for H.225.
*Mar 12 04:03:57.169: H225Lib::h225TAccept: TCP connection accepted from 172.16.70.228:2328 on
socket [1]
*Mar 12 04:03:57.169: H225Lib::h225TAccept: Q.931 Call State is initialized to be [Null].
*Mar 12 04:03:57.177: Hex representation of the received TPKT03000065080000100
The following debug output shows that the H.225 data is coming from the Cisco CallManager on
this TCP session. Important to notice in this debug output is the protocolIdentifier, which
indicates the H.323 version being used. The following debug shows that H.323 version 2 is being
used. The called and calling party numbers are also shown.
- Source Address H323-ID
- Destination Address e164