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.

Communication Manager Maintenance Object Repair Procedures<br />

BRI Remote Loopback Test (#627)<br />

This test checks the integrity of a circuit-switched B-Channel connection between the switch<br />

and the endpoint.<br />

The endpoint is put in the “maintenance busy” state to prevent the switch from entering calls to<br />

the endpoint during the test. An application message containing a loopback activate request for<br />

the appropriate B-Channel is sent to the endpoint. The endpoint responds with a loopback<br />

activated response. The switch then sends data to the endpoint over the B-Channel under test.<br />

Since the B-Channel is looped back at the endpoint, maintenance should receive the data that it<br />

sent. If no data is detected, the test fails. The switch then releases the endpoint so that it is<br />

available to terminate calls.<br />

This test is not executed for ASAI adjuncts because adjuncts do not support MIMs upon which<br />

this test is based. This test is run on BRI-SET, Various Adjuncts.<br />

Table 517: BRI Remote Loopback Test (#627) 1 of 4<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1000 ABORT Could not seize the endpoint or B-Channels for test.<br />

1. Retry the command at 1-minute intervals up to 5 times.<br />

2. If the test continues to abort, escalate the problem.<br />

1005 ABORT The endpoint’s MIMs <strong>Support</strong>ed field is administered to “no.”<br />

1. Enter change station extension to change the field only if the<br />

endpoint documentation reflects support for ISDN-BRI Management<br />

and Maintenance Procedures.<br />

1113 ABORT The signaling link between the switch and the endpoint is down.<br />

1. Enter test port location long to clear any errors that prevent<br />

establishment of the signaling link.<br />

2. Examine the results of the Signaling Link Status test (#626) that is run<br />

as part of this command. If this test aborts or fails, follow the repair<br />

procedure for Signaling Link Status Test (#626).<br />

3. If the XID test (#628) continues to abort, escalate the problem.<br />

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

1 of 4

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

Saved successfully!

Ooh no, something went wrong!