Remote H323 Gateway Is Not Reachable—Signaling (86) - Cisco BTS 10200 Troubleshooting Manual

Chapter 10 Signaling Troubleshooting
Remote H323 Gateway is not Reachable—Signaling (86)
The Remote H323 Gateway is not Reachable alarm (major) indicates that the remote H323 gateway is
not reachable. The primary cause of the alarm is that a loss of communication with a remote gateway has
occurred. To correct the primary cause of the alarm, perform the standard connectivity tests–both the
physical checks and the IP tests. Also, ensure that the gateway is not out of service.
H323 Message Parsing Error—Signaling (87)
The H323 Message Parsing Error alarm (major) indicates that a H323 message parsing error has
occurred. The primary cause of the alarm is that the system was unable to successfully parse an incoming
H323 message. This alarm is a result of either a software bug or bad message being received–a message
with a valid message type but an invalid field within the message. To correct the primary cause of the
alarm, snoop the message from the endpoint and verify its content or contact Cisco TAC.
Note Refer to the
detailed instructions on contacting Cisco TAC and opening a service request.
H323 Message Encoding Error—Signaling (88)
The H323 Message Encoding Error alarm (major) indicates that a H323 message encoding error has
occurred. The primary cause of the alarm is that the system was unable to encode an H323 message for
sending. The alarm is indicative a software bug. To correct the primary cause of the alarm, contact Cisco
TAC.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Gatekeeper not Available/Reachable—Signaling (89)
The Gatekeeper not Available/Reachable alarm (major) indicates that the gatekeeper is not available or
the gatekeeper is not reachable. The primary cause of the alarm is that the gatekeeper is not available or
is unreachable. To correct the primary cause of the alarm, check the network connectivity. Check to
ensure the GK is reachable by trying to ping the GK IP address. If reachable, then check to ensure that
the GK is configured up.
Alternate Gatekeeper is not Responding—Signaling (90)
The Alternate Gatekeeper is not Responding alarm (major) indicates that the alternate gatekeeper is not
responding. The primary cause of the alarm is that the alternate gatekeeper is not responding. To correct
the primary cause of the alarm, check network connectivity. Check to ensure the alternate GK is
reachable by trying to ping the alternate GK IP address. If reachable, then check to ensure that the
alternate GK is configured up.
OL-8723-19
"Obtaining Documentation and Submitting a Service Request" section on page lvi
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Troubleshooting Signaling Alarms
for
for
10-141