Error type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures.

Error type 1: Failure of the IP-PROCR carrying the signaling group channel.

Error type 18: The signaling group in question has been busied out by command. Release the signaling group, if appropriate, with release signaling-group grp#.

Error type 257: Tracks failures of the H.323 signaling-group PING test. See Signaling Group Ping Test 1387 for test failure information.

Error type 513: Tracks excessive round-trip delay of the H.323 signaling-group PING test, if the round-trip delay exceeds 4 seconds. See Signaling Group Ping Test 1387 for test failure information.

Error type: 770: Tracks excessive latency and packet-loss from background IP measurements collected by the VOIP media module. Indicates that test packets sent from a VOIP media module to the far-end IP address specified on the signaling group form have exceeded the IP latency and loss thresholds, as administered on the system-parameters ip-options screen. Exceeding these thresholds indicates that the IP network may not be providing sufficient quality of service for adequate transmission of voice. If the signaling group has been administered to enable BYPASS, then Error Type 1025 also occurs.

Error type 1025: The signaling group has been placed into a BYPASS condition because of IP network congestion. The signaling group accepts incoming calls, but every outgoing call is denied. The system routes these calls over a secondary route, if one has been administered.

Error type 1281: No media resources are in service to provide VoIP connections for the trunk members of the signaling group.

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 media resource in-service for its signaling group.

This error places the H323 B-Channels into an out-of-service far-end state.

Error type 1794: The Signaling Group reported that the far end has detected excessive packet latency or loss. This error places the H323 B-Channels into an out-of-service far-end state.

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.

Error type 2305: The Gateway, the 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 RRQfield set to y.

Error type 2561: The signaling group is registered to a Survivable Remote Server.

Error type 2817: The T303 timer timed out. Notification only, no action is necessary.

Error type 3585: Layer 3 test failed. The far-end is not available. See H.323 Signaling Layer 3 test 1673 for more information.

Error types 3842 - 3942: These error types report certain error messages received by the H.323 Signaling Group for the D-Channel. The Aux datafield shows for which D-Channel 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. The table provides more information.