Demand test descriptions and error codes - Avaya Support

PE-BCHL (PRI Endpoint Port)
automatically try to recover by clearing the call (the call will be torn down). Use status
pri-endpoint extension to determine the state of the port.
When running the short test sequence, note the results of the Call State Audit Test (#257).
c. Error Type 15: software audit error that does not indicate any hardware malfunction. Run
the short test sequence, and investigate associated errors.
d. Error Type 18: the PRI endpoint port has been busied out by busyout pri-endpoint
extension or busyout port location. No wideband calls can be made to this port,
although wideband calls can still be made to other ports within this PRI endpoint if they are
in service. Release the port with release port location.
e. Error Type 129: the far-end terminal adapter changed its ISDN service state to
out-of-service or maintenance. This may be a temporary condition due to testing of this port
by the far-end terminal adapter or a hardware problem with the port. Outgoing calls to the
terminal adapter will not be allowed over the port, although calls can still be made to other
ports that are in service within the same PRI endpoint. To investigate the status of the port,
enter status pri-endpoint extension.
f. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes. To clear the error, reinsert or replace the circuit pack.
g. Error Types 257, 769: disagreement between this switch and the terminal adapter at the
other end of the connection with regard to the ISDN service state of the PRI endpoint port.
The switch will automatically try to recover by performing a service state audit. Use status
pri-endpoint extension to determine the state of the port.
When running the short test sequence, note the results of the Service State Audit Test
(#256).
h. Error Type 513: This port is not recognized by the far-end terminal adapter. Investigate the
PRI endpoint administration for both the switch and the terminal adapter, and make sure
they agree.
i. Error Type 1281: The Conference Circuit test (#7) failed on this port. See Conference
Circuit Test (#7) for repair procedures.
j. Error Type 1537: The NPE Crosstalk test (#6) failed on this port. See NPE Crosstalk Test
(#6) for repair procedures.
k. Error Type 1793: failure of the UDS1 Interface circuit pack. Run the short test sequence
and note the results of the Signaling Link State Audit Test (#255).
l. Error Type 3073: Two Service State audit attempts have failed (see Service State Audit
Test (#256)). The port will not be usable for any outgoing calls to the terminal adapter until
the test passes and the port state is changed to in-service. Incoming calls from the terminal
adapter will be accepted over this port, and other ports in the PRI endpoint can still be used
for both incoming and outgoing calls to and from the terminal adapter.
Issue 5 May 2009 715