19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - 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.

T305 ISDN T305 timeout<br />

T3081 ISDN T3081 timeout<br />

T3082 ISDN T3082 timeout<br />

TL3 Status Inquiry<br />

T304 Setup ACK<br />

T310 Call Proceeding Receive<br />

T313 Connect SEND<br />

TBRI-PT (ISDN Trunk-Side BRI Port)<br />

i. Error Type 1281: this <strong>error</strong> occurs when the BRI NPE Crosstalk <strong>test</strong> (#617) has failed. The<br />

<strong>test</strong> will be repeated every 15 minutes until it passes. Follow normal trouble shooting<br />

procedures for BRI NPE Crosstalk Test (#617). If this does not fix the problem, follow<br />

normal escalation procedures.<br />

j. Error Type 1537: the board received a bad Cyclical Redundancy Check (CRC) over the<br />

D-chel. This <strong>error</strong> is reported on a per-port basis. When the CRC <strong>error</strong>s exceed 5 within 15<br />

minutes, the port is taken out of service for 5 seconds. If 5 more CRC <strong>error</strong>s are received<br />

within 15 minutes of the first set of 5 <strong>error</strong>s, the port is taken out of service for 1 minute. If 5<br />

more CRC <strong>error</strong>s are received within 15 minutes of the previous 5, the port is taken out of<br />

service for 15 minutes.<br />

This <strong>error</strong> is most likely due to a problem with backplane wiring, a noise source, or no<br />

termination (an open circuit). It usually does not indicate a problem with the circuit pack.<br />

1. Check the backplane wiring.<br />

2. If the problem persists escalate the problem.<br />

k. Error Type 1538: this <strong>error</strong> occurs when a frame with a bad CRC is received over the TDM<br />

D-chel by the BRI trunk board. This <strong>error</strong> only occurs on a system that switches the packet<br />

implementation of the D-chel over the TDM bus. This <strong>error</strong> indicates an off-board problem<br />

related to the packet implementation of the TDM D-chel.<br />

l. Error Type 1793: the BRI Port Local TDM Looparound <strong>test</strong> (#619) failed. Run the long <strong>test</strong><br />

sequence, <strong>and</strong> check the results of the BRI Port Local TDM Looparound Test (#619).<br />

m. Error Type 2049: the BRI Layer 3 Query Test (#1243) has determined that the signaling link<br />

is down (Layer 2). The <strong>test</strong> is repeated every 15 minutes until it passes.<br />

n. Error Type 2305: the BRI Layer 3 Query Test (#1243) failed. The <strong>test</strong> is repeated every 15<br />

minutes until it passes.<br />

o. Error Type 2561: loss of Layer 1 in stable configuration. The BRI port is configured as<br />

stable but the Trunk-side Layer 1 Query Test (#1242) failed 6 times within one hour. Change<br />

the layer 1 stable field on the change bri-trunk-board screen<br />

to n.<br />

p. Error Type 3073: a frame of information had to be repeated or deleted. Slips usually occur<br />

when the received bit rate is not synchronized with the TDM bus clock.<br />

q. Error Type 3585: the circuit pack detected an overflow of its receive buffers. This <strong>error</strong><br />

occurs only a system that switches the packet implementation of the D-chel over the TDM<br />

Issue 5 May 2009 945

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

Saved successfully!

Ooh no, something went wrong!