H.323-SGR error log entries and recommended actions

Last Updated : Sep 13, 2023 |
Table 1: H323-SGR error log entries

Error type

Aux data

Associated test

Alarm level

On/off board

Command to resolve the error

0

0

Any

Any

test signaling-group grp#

1

Any

Ethernet port status test (#1386)

Min

Off

test signaling-group grp#

18

0

busyout signaling-group grp #

WRN

Off

release signaling-groupgrp#

257

Any

Signaling group ping (#1387)

Min

Off

test signaling-groupgrp#

513

Any

Signaling group ping (#1387)

WRN

Off

test signaling-groupgrp#

770

Any

WRN

Off

1537

Any

2049

Keep alive failure

Min

Off

2305

Gateway unregistered inline error

Min

Off

2561

Any

Registered to Survivable Remote Server Inline Error

Min

Off

2817

T303 Timer timed out

3585

Layer 3 Test (#1673)

Min

Off

3841 - 3942

Any

Notes:
  1. 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.

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

  3. 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#.

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

  5. 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.

  6. 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.

  7. 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.

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

  9. 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.

  10. 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.

  11. 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.

  12. 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.

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

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

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

  16. 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.

    Table 2: Descriptions and recommendations for error types 3842-3942

    Error code

    Description

    Recommendation

    3842

    A request has been made to use a transit network or common carrier that cannot be accessed.

    The equipment sending this cause event does not recognize the transit network.

    1. From the circuit pack or media module and port number, in the Aux data field, determine the trunk group against which the error was reported.

    2. Check every routing pattern containing this trunk group for validity of interexchange carriers requested (IXC field).

    3843

    No route to destination. Request received to route call through a transit network that is recognized but not allowed to carry the call or not able to serve the destination.

    3846

    The far-end switch has indicated that the B-Channel trunk is not acceptable for use in the call for which it was requested.

    This could indicate an administration problem. For example, the local switch and the far-end switch have different B-Channels administered, or could reflect the occurrence of a normal race condition. For example, the local switch has requested use of a B-Channel that the far-end switch had just reserved for use on another call.

    1. From the media module and port number in the Aux Data field, determine the trunk group against which the error was reported.

    2. Enter status trunk for the indicated trunk. Refer to DS1 ISDN Trunk Service Statesand ISDN-PRI Trunk Service States sections of ISDN-TRK for recovery suggestions.

    3858

    Similar to error type 1. The switch sent a message to the far-end switch or terminal adapter that did not respond in the time allowed.

    Follow same recommendations as for error type 1.

    3878

    The far-end switch has indicated that the network is not functioning correctly and that the condition may last a relatively long period of time. For example, immediately re-attempting the call may not be successful.

    Network is out-of-order.

    1. From the media module and port number in the Aux datafield, determine the trunk group against which the error was reported.

    2. Consult with the network provider to determine the nature and expected duration of the out-of-service condition.

    3. Consider modifying every routing pattern containing this trunk group to route calls around the network that is out-of-service.

    3890

    A request to use a network service has been denied. Administration somewhere on the network has indicated that the requested service has not been subscribed to, or purchased for this trunk.

    This could be a local administration problem only, or a mismatch between the local administration and that of the network provider.

    1. From the media module and port number in the Aux data field, determine the trunk group against which the error was reported.

    2. Display the trunk group screen: If the trunk group is Call-by-Call, the service type is cbc, check every routing pattern form containing this trunk group to see if the Service/Feature Service/Featurefields contain the correct network services purchased for this trunk. If the trunk group is not Call-by-Call, check that the service type field contains the single network service purchased for this trunk.

    3. If local administration is correct, consult with the customer or the network provider to determine the services that the customer has subscribed to for this trunk group.

    3892

    Protocol detail may offer a clue if the customer is having calls denied with an unexpected intercept tone.

    If the customer is complaining of unexpected intercept tones and no other cause can be found, escalate the problem and provide the next tier with this error log information.

    3894

    Protocol detail; may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone.

    First, eliminate any transitory state mismatch problems by entering test port location for the trunk port shown in the Aux data field. Service State Audit Test 256 is the important test in the sequence. If this passes satisfactorily, yet the customer continues to complain of unexpected intercept tones and no other cause can be found, escalate the problem and provide the next tier with this error log information.

    3902

    FRANCE ONLY: Service not authorized.

    3903

    Service or option not available, unspecified. This cause reports a service or option not available event only when no other cause in the service or option not available class applies.

    3905

    Protocol detail; may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone.

    If customer is complaining of unexpected intercept tones and no other cause can be found, escalate the problem and provide the next tier with this error log information.

    3906

    Protocol detail may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone.

    If customer is complaining of unexpected intercept tones and no other cause can be found, escalate to the problem and provide the next tier with this error log information.

    3909

    A request to use a network service has been made, but the network has rejected the request because the requested service is not implemented.

    Follow the previous recommendation for error type 3890.

    3910

    Only restricted digital BC available.

    3919

    Service or option not implemented, unspecified. Used when no other cause in this class applies.

    3928

    A call was denied because of a basic incompatibility existed between the type of call and either the facilities selected by the routing pattern or the called user.

    This error might be helpful as a clue if the customer complains of receiving unexpected intercept tone. Determine the trunk group from the circuit pack or media module and port number in the Aux data field and then check the BCC fields of the pertinent routing patterns. Also, investigate whether or not the calling and called endpoints are compatible. For example, some switches may not allow a voice station to call a data extension.

    3942

    Timer expiry: T310 time-out, no answer to call proceeding.