Demand test descriptions and error codes - Avaya Support

H323-SGR (H.323 Signaling Group)
h. Error Type 1281: No media processor resources are in service to provide VoIP connections
for the trunk members of the signaling group.
Check for errors against the MEDPRO and MEDPROPT maintenance objects. This error
causes all H323 B-Chels to be in an out-of-service near-end state.
i. Error Type 1537: The far end of the signaling group is not ready to handle audio bearer. If
the other end of this signaling group is also a Communication Manager server, this error
means the server on the other end does not have MEDPRO in-service for its signaling
group.
This error places the H323 B-Chels into an out-of-service far-end state.
j. Error Type 1794: The Signaling Group reported that the far end has detected excessive
packet latency or loss. This error places the H323 B-Chels into an out-of-service far-end
state.
k. Error Type 2049: A Keep-Alive timer is set for every registered endpoint on the Remote
Office, and the switch expects Keep-Alive updates within that timer’s time period. If the
update does not occur, an error is logged against REM-OFF as well as H323-SGR. The
error against H323-SGR generates a Minor alarm. This error is only valid if the change
signaling-group screen has the RRQ field set to y. The Keep-Alive Error Type 2049
clears only after a registration occurs and Error Type 2305 clears.
l. Error Type 2305: The Gateway (signaling group on the Remote Office) is unregistered. The
error against H323-SGR generates a Minor alarm when this failure occurs. This error is
valid only if the change signaling-group screen has the RRQ field set to y.
m. Error Type 2561: The signaling group is registered to an LSP.
n. Error Type 2817: The T303 timer timed out. Notification only, no action is necessary.
o. Error Type 3585: Layer 3 test failed. The far-end is not available. See H.323 Signaling
Layer 3 Test (#1673) for more information.
p. Error Types 3842 - 3942: These Error Types report certain error messages received by the
H.323 Signaling Group for the D-Chel. The aux data field shows for which D-Chel the
message was received.
The error code generated equals 3840+x, where “x” is a cause value. There is no
recommended action for these Error Types. No direct action or alarming is performed.
They provide added data that may be useful when tracking down obscure networking and
routing problems. Table 136: Descriptions and Recommendations for Error Types
3842-3942 provides more information.
Issue 5 May 2009 495