09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PE-BCHL (PRI Endpoint Port)<br />

e. Error Type 129: the far-end terminal adapter changed its ISDN service state to<br />

out-of-service or maintenance. This may be a temporary condition due to testing of this port<br />

by the far-end terminal adapter or a hardware problem with the port. Outgoing calls to the<br />

terminal adapter will not be allowed over the port, although calls can still be made to other<br />

ports that are in service within the same PRI endpoint. To investigate the status of the port,<br />

enter status pri-endpoint extension.<br />

f. Error Type 130: the circuit pack has been removed or has been insane for more than 11<br />

minutes. To clear the error, reinsert or replace the circuit pack.<br />

g. Error Types 257, 769: disagreement between this switch and the terminal adapter at the<br />

other end of the connection with regard to the ISDN service state of the PRI endpoint port.<br />

The switch will automatically try to recover by performing a service state audit. Use status<br />

pri-endpoint extension to determine the state of the port.<br />

When running the short test sequence, note the results of the Service State Audit Test<br />

(#256).<br />

h. Error Type 513: This port is not recognized by the far-end terminal adapter. Investigate the<br />

PRI endpoint administration for both the switch and the terminal adapter, and make sure<br />

they agree.<br />

i. Error Type 1281: The Conference Circuit test (#7) failed on this port. See Conference<br />

Circuit Test (#7) for repair procedures.<br />

j. Error Type 1537: The NPE Crosstalk test (#6) failed on this port. See NPE Crosstalk Test<br />

(#6) for repair procedures.<br />

k. Error Type 1793: failure of the UDS1 Interface circuit pack. Run the short test sequence<br />

and note the results of the Signaling Link State Audit Test (#255).<br />

l. Error Type 3073: Two Service State audit attempts have failed (see Service State Audit<br />

Test (#256)). The port will not be usable for any outgoing calls to the terminal adapter until<br />

the test passes and the port state is changed to in-service. Incoming calls from the terminal<br />

adapter will be accepted over this port, and other ports in the PRI endpoint can still be used<br />

for both incoming and outgoing calls to and from the terminal adapter.<br />

m. Error Type 3585: the switch received an ISDN RESTART message for an ISDN port that is<br />

not idle. Because calls are not typically cleared with the RESTART message, this Error<br />

Type may be associated with a dropped call report from a user.<br />

The following Aux Data values for Error Type 3585 represent the port’s ISDN call state at<br />

the time the unexpected RESTART request was received from the terminal adapter. This<br />

information can be useful if dropped calls are being reported by users of the PRI endpoint.<br />

Aux Data values that do not appear below can be ignored.<br />

Communication Manager Release 5.0 Issue 4 January 2008 1079

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!