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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 60: ISDN-BRI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Notes) 4 of 4<br />

Error<br />

Code<br />

Test Result Description / Recommendation<br />

81 Invalid CRV An invalid CRV was sent by the adjunct.<br />

1. This may indicate a CRV inconsistency between the switch <strong>and</strong><br />

the adjunct. Refer to the CallVisor protocol reference manual.<br />

2. If step 1 does not resolve the problem, escalate to the next tier.<br />

j. Error 2568: the adjunct ID is invalid, check the vender ID or software running on the <strong>Avaya</strong><br />

adjunct<br />

k. Error Type 2817: there is a layer-2 problem over the D-Chel between the switch <strong>and</strong> the<br />

endpoint. When this <strong>error</strong> occurs, an alarm is raised against the station or adjunct. Execute<br />

<strong>test</strong> station extension short <strong>and</strong> note the results of the BRI XID <strong>test</strong> (#628). If this<br />

<strong>test</strong> fails, follow the repair procedure for BRI XID Test (#628).<br />

l. Error Type 3073: there is a problem with the B-Chel connection between the switch <strong>and</strong> the<br />

endpoint. When this <strong>error</strong> occurs, a warning alarm is raised against the endpoint. Execute<br />

<strong>test</strong> station extension long <strong>and</strong> note the results of the BRI Remote Loopback Test<br />

(#627). If this <strong>test</strong> fails, follow the repair procedure for BRI Remote Loopback Test (#627).<br />

m. Error Type 3329: occurs whenever the point-to-point signaling link to the endpoint goes<br />

down (except when it goes down because either the PKT-BUS has failed or has been<br />

busied out by system technician). When this <strong>error</strong> occurs, an alarm is raised against the<br />

endpoint or adjunct. Execute <strong>test</strong> station extension short <strong>and</strong> note the results of<br />

the Signaling Link Status <strong>test</strong> (#626). If this <strong>test</strong> fails, follow the repair procedure for<br />

Signaling Link Status Test (#626). The alarm is retired when the signaling link is<br />

reestablished to the endpoint or adjunct.<br />

n. Error Type 3584-3839: Certain ASAI protocol-specific cause <strong>codes</strong> are logged by switch<br />

software. The cause code can be determined from the following formula:<br />

If the Error Type is greater than 3712, then the ASAI cause code is equal to the Error Type<br />

minus 3712. This code was sent to the adjunct by the switch.<br />

If the Error Type is less than 3712, then the ASAI cause code is equal to the Error Type<br />

minus 3584. This code was sent to the switch by the adjunct.<br />

A description of the various ASAI cause values is contained in the Table 61: ASAI CAUSE<br />

VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes). This table also contains<br />

recommended actions associated with the cause value. In addition, the Aux Data field of<br />

the Error Log entry contains additional diagnostic information additional diagnostic.<br />

230 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

4 of 4

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

Saved successfully!

Ooh no, something went wrong!