ISDN-TRK error log entries and recommended actions

Last Updated : Sep 13, 2023 |
Table 1: ISDN-TRK Error Log Entries

Error type

Aux data

Associated test

Alarm level

On/Off board

Command to resolve the error

0

0

Any

Any

Any

test port location

1

Any

test port location

15

Any

Port Audit and Update Test (#36)

18

0

busyout trunk grp#/mem#

release trunk grp#/mem#

19

0

129

WRN

OFF

test port location

130

WRN

ON

test port location

257

Any

test port location

513

Any

WRN

OFF

test port location

769

Any

test port location

1025

0

1281

Any

Conference Circuit Test (#7)

MAJ MIN WRN 1

ON

test port location l r 4

1537

Any

NPE Crosstalk Test (#6)

MAJ MIN WRN

ON

test port location l r 3

1793

Any

test port location

3073

Any

Service State Audit (#256)

test port location

3585

Any

3841

Any

WRN

OFF

1. Major or minor alarms may be downgraded to Warning alarms based on the value used in set options.

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: Disagreement between this switch and the switch at the other end of the trunk connection with regard to the ISDN call state of the DS1 ISDN Trunk. This switch will automatically try to recover by clearing the call, that is, call will be torn down. You can use status trunk grp#/mem# to determine the state of the trunk.

    When running the short test sequence, note the results of the Call State Audit Test 257.

  3. Error type 15: Software audit error and does not indicate a hardware malfunction. Run the short test sequence, and investigate associated errors.

  4. Error type 19: Possible protocol mismatch or far end may be out of service.

  5. Error type 129: The far-end switch changed its ISDN service state to either out of service or maintenance. This may be either a temporary condition due to far-end testing of that trunk or a hardware problem with the trunk. Outgoing calls will not be allowed over the trunk. To investigate the status of the trunk, enter status trunk grp#/mem#.

  6. Error type 130: The media module has been removed or has been insane for more than 11 minutes. To clear the error, reinsert or replace the media module.

  7. Error types 257 and 796: Disagreement between this switch and the switch at the other end of the trunk connection with regard to the ISDN service state of the DS1 ISDN Trunk. This switch will automatically try to recover by performing a service state audit. You can use status trunk grp#/mem# to determine the state of the trunk.

    When running the short test sequence, note the results of the Service State Audit Test 256.

  8. Error type 513: This trunk is not recognized by the far-end switch. Investigate the trunk administration for both switches and make changes as necessary.

  9. Error type 1025: An unexpected SERVICE or SERVICE ACK was received. Possibilities include:

    • Translations conflict.

    • Protocol differences.

    • Survivable Core Server may be using NI3 protocol, not currently implemented in Communication Manager.

    • B-Channel negotiation problem (glare).

  10. Error type 1793: failure of the DS1 media module. When running the short test sequence, the results of the Signaling Link State Audit Test 255 are important.

  11. Error type 3073: Service State Audit Test 256 failed. The trunks will not be usable for any outgoing calls (although incoming calls will be accepted) until the test passes and the trunk state is changed to in service. To investigate trunk status use status trunk grp#/mem#.

  12. Error type 3585: the switch receives an ISDN RESTART message for an ISDN trunk. Calls are cleared with the RESTART message. Therefore, this Error Type may be associated with a dropped call report from a user.

    The following Aux Data values for Error type 3585 represent the trunk’s ISDN call state at the time the unexpected request to restart the channel was received from the remote switch. This information can be useful if dropped calls (cutoffs) are reported by users of the ISDN-PRI trunks.

    The meanings of Aux Data values are shown below; ignore any others.

    Table 2: ISDN Trunk - Error 3585 Aux Data Values

    Aux Data

    Cause

    0

    A idle trunk received a restart.

    10

    A call in a stable, talking state was cleared unexpectedly by the far end with an ISDN RESTART message. This state is called the active state.

    4,

    7,

    8, 260, 263

    A call that has not reached the active state, but has at least reached a ringing state, was cleared unexpectedly by the far end with an ISDN RESTART message.

    1,

    3,

    6,

    9, 265

    A call that has not yet reached a ringing state was cleared unexpectedly by the far end with an ISDN RESTART message.

    11, 12, 19, 531, 267, 268

    A call that was in the process of clearing anyway has been cleared by the far end with an ISDN RESTART message. If this condition occurs frequently, it may mean that the far end is attempting to clear trunks that it thinks are in a hung state. The RESTART message brings the trunk to an idle condition.

  13. Error type 3841: An ISDN trunk selected by the near end has been rejected 10 times by the far end without a successful call. This may indicate a service-state mismatch between the near and far ends for this trunk that is affecting the end user that is, customer receives unexpected intercept tones when accessing ISDN trunks. This may indicate that the ISDN trunk is not administered at the far end.

    The Aux field contains the physical name of the ISDN trunk in decimal. Using this decimal name, verify that the far end has this trunk administered.

    The Warning alarm will be retired automatically whenever an outgoing or incoming call that uses this trunk is answered by the called endpoint. If problems persist, then busyout the ISDN trunk to take it out of the hunt group.