09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

Communication Manager Maintenance Object Repair Procedures<br />

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

Error<br />

Code<br />

Test Result Description / Recommendation<br />

34 No circuit or<br />

channel<br />

available<br />

42 Switch<br />

Equipment<br />

Congestion<br />

50 Requested<br />

Facility Not<br />

Subscribed<br />

A resource on the switch is unavailable for a call. For BRI endpoints:<br />

This cause value is not logged. For ASAI or <strong>Avaya</strong> Adjuncts: This<br />

condition means that there are no available trunks for an outgoing<br />

call request.<br />

1. Verify that the adjunct is administered to support the trunk<br />

capabilities of the switch.<br />

2. Investigate trunk group status by entering status trunk<br />

commands from the SAT or by requesting a trunk group query<br />

or queries from the adjunct.<br />

3. Perform trunk diagnostic procedures such as test trunk.<br />

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

Switch takes control to limit received traffic. For BRI endpoints: This<br />

cause value is not logged. For ASAI or <strong>Avaya</strong> Adjuncts:<br />

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

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

Requested facility is implemented, but not administered. Potential<br />

administration problem with endpoint or adjunct. For BRI endpoints:<br />

1. Verify the switch administration of endpoint using display<br />

station or display data-module.<br />

2. If step 1 does not resolve the problem, refer to the endpoint’s<br />

service manual and verify administration on the endpoint.<br />

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

For ASAI adjuncts:<br />

1. Display the Customer Optional Features screen (administration<br />

screen) on the switch to determine which ASAI capabilities are<br />

turned on in the switch.<br />

2. Verify that the adjunct is administered to support the identical<br />

capabilities as the switch. If there is a mismatch in the<br />

administered capabilities, then re-administer the switch and/or<br />

the adjunct to establish a consistent set of desired capabilities<br />

on both the switch and the adjunct.<br />

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

For <strong>Avaya</strong> adjuncts:<br />

1. Display the Customer Optional Features screen (administration<br />

screen) on the switch to determine whether the <strong>Avaya</strong> adjunct<br />

is set enabled on in the switch.<br />

2. If Error Type 2567 or 2568, verify the <strong>Avaya</strong> adjunct version,<br />

and re-administer if needed.<br />

3. If step 2 does not fix the problem, escalate to the next tier of<br />

support<br />

604 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s<br />

2 of 3

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

Saved successfully!

Ooh no, something went wrong!