ISDN-SGR error log entries and recommended actions

Last Updated : Sep 13, 2023 |
Table 1: ISDN-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

257

Any

test signaling-group grp#

513

Any

test signaling-group grp#

769

Any

Primary Signaling Link Hardware Check (#636)

test signaling-group grp#

1025

Any

Secondary Signaling Link Hardware Check (#639)

test signaling-group grp#

1793

Any

Layer 2 Status Test (#647)

WRN

OFF

test signaling-group grp#

2049

Any

Layer 2 Status Test (#647)

WRN

OFF

test signaling-group grp#

2305

Any

Remote Layer 3 Query (#637)

MIN

OFF

test signaling-group grp#

3585

Port number

3842 – 3942

Port number
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: This switch sent a message to the far-end switch or terminal adapter, and the far end did not respond in the allotted time. Possible causes include link failure and congestion or outage at the far end. The Aux Data field contains layer-3 protocol information used by internal counters.

    If no other symptoms are present, no action is required. If layer-3 communication is down, there should be indications in the screen of alarms and errors for link components. Check for other errors against ISDN-SGR, ISDN-TRK, and other hardware components on the link.

    There is no test to clear these errors. An error counter is decremented by 1 every 15 minutes, and the error eventually will be cleared by the system.

  3. Error type 257: the primary signaling channel connection has been lost for more than 90 seconds. If a secondary signaling channel does not exist or is not in service, the associated B-Channels will be placed in the ISDN Maintenance/Far-End state. The B-Channels will not be usable for outgoing calls, although incoming calls will still be accepted. The switch will automatically attempt to recover the signaling link. Check the results of the Primary Signaling Link Hardware Check 636 in the test sequence. When the link does recover, the B-Channels will be negotiated back to the In-Service state and their alarms will be retired.

    When this error occurs, the state of the Signaling Group is changed to out of service. Verify this with status signaling-group grp#.

  4. Error type 513: The secondary signaling channel connection has been lost for more than 90 seconds. If the primary signaling channel is not in service, B-Channels will be placed in the ISDN Maintenance/Far-End state. The B-Channels will not be usable for outgoing calls, although incoming calls will still be accepted. The switch will automatically attempt to recover the signaling link. Note the results of the Secondary Signaling Link Hardware Check 639. When the link does recover, the B-Channels will be negotiated back to the In-Service state and their alarms will be retired.

    When this error occurs, the state of the Signaling Group is changed to out of service. You can verify this using status signaling-group grp#.

  5. Error type 1793: The Layer 2 Query Test failed for the primary signaling channel. See Layer 2 Status Query Test 647.

  6. Error type 2049: The Layer 2 Query Test failed for the secondary signaling channel. See Layer 2 Status Query Test 647.

  7. Error type 2305: The Remote Layer 3 Query 637 failed. A specific message was sent to the far-end switch, and it did not respond within the time allowed. Investigate elements of the ISDN PRI D-Channel(s) ISDN-PLK (ISDN-PRI Signaling Link Port) for both this switch and the far-end switch. If Test #637 fails twice in a row, the B-Channels will be alarmed and made unavailable for outgoing calls although the incoming calls will still be accepted. When Test #637 succeeds and the far-end switch starts responding properly, the DS1 ISDN Trunk (B-Channels) will be placed back into normal operation, and their alarms will be retired.

  8. Error type 3585: A SERV or SERV ACK ISDN D-channel message has been received by a non-US-type interface (country option other than 1 on the DS1 Administration screen). However, these messages are used only for NFAS D-channel backup signaling that is supported only by country protocol 1.

    Thus, there may be a mismatch in administration between the local and far-end switches. Consult with the customer’s network provider to determine whether the D-Channel is set up correctly at the far-end switch.

  9. Error types 3842 - 3942: These Error Types report certain error messages received by the ISDN-PRI Signaling Group for one of its associated B-Channels. The aux data field shows for which B-Channel (port number) the message was received.

    The error code generated equals 3840+x, where x is a cause value defined by the ISDN-PRI Specification. Note that there is no recommended action for these Error Types; selected ISDN cause values are placed in the log when they are received, but no direct action or alarming is performed solely in response to receiving them. They provide added data that may prove 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 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 the DS1 ISDN Trunk Service States and ISDN-PRI Trunk Service States sections of ISDN-TRK for recovery suggestions.

    3858

    Similar to Error Type 1. The switch sent an ISDN 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 Data field, 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 (e.g., SDN) 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 form: If the trunk group is Call-by-Call (Service Type is cbc), check every routing pattern form containing this trunk group to see if the Service/Feature fields 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 and/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 customer is having ISDN calls denied with an unexpected intercept tone.

    If customer is complaining of unexpected intercept tones when accessing ISDN trunks or PRI endpoints 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 when accessing ISDN trunks or PRI endpoints 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 when accessing ISDN trunks or PRI endpoints 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 when accessing ISDN trunks or PRI endpoints 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 after accessing ISDN trunks or PRI endpoints. 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 ISDN switches may not allow a voice station to call a data extension.

    3942

    Timer expiry: T310 time-out, no answer to CALL PROCEEDING.