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 421: Signaling Link Status Test (#626) 2 of 2<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

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

1187 ABORT The circuit pack, port, or station may have been busied out by comm<strong>and</strong>.<br />

1. Look in the Error Log for Error Type 18 (busied out) for ASAI-BD,<br />

ASAI-PT, ASAI-EPT, BRI-BD, BRI-PORT, or BRI-SET.<br />

2. If this Error Type is present for ASAI-EPT or BRI-SET only, enter<br />

release station extension <strong>and</strong> run the <strong>test</strong> again.<br />

3. If this Error Type is present for ASAI-PT <strong>and</strong> ASAI-EPT or<br />

BRI-PORT <strong>and</strong> BRI-SET, use release port location <strong>and</strong> run<br />

the <strong>test</strong> again.<br />

4. If this Error Type is present for ASAI-BD, ASAI-PT, <strong>and</strong> ASAI-EPT or<br />

BRI-BD, BRI-PORT, <strong>and</strong> BRI-SET, enter release board<br />

location <strong>and</strong> run the <strong>test</strong> again.<br />

2012 ABORT Internal system <strong>error</strong>.<br />

2100 ABORT Could not allocate the necessary system resources to run this <strong>test</strong>.<br />

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

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

1113 FAIL The signaling link is not “bound” to the adjunct or endpoint.<br />

For BRI endpoints supporting MIM initialization, this <strong>error</strong> indicates<br />

that the endpoint has not been bound to a signaling link (that is,<br />

SPID initialization has not been completed). Since the signaling link<br />

associated with the endpoint is not identified until SPID initialization<br />

completes, this <strong>error</strong> does not imply that the signaling link is<br />

connected or disconnected at Layer 2 nor does it provide the status<br />

of TEI assignment for the endpoint.<br />

For ASAI adjuncts <strong>and</strong> BRI endpoints not supporting MIM<br />

initialization, this <strong>error</strong> indicates that the link is disconnected at<br />

Layer 2. Since the signaling link associated with the endpoint has<br />

been identified via administration, the link is only “unbound” from the<br />

endpoint when it is disconnected.<br />

1. Enter status bri-port location <strong>and</strong> see the associated<br />

procedures in BRI-PORT (ISDN-BRI Port).<br />

PASS The signaling link is connected at Layer 2 <strong>and</strong> “bound” to the BRI endpoint<br />

or ASAI adjunct.<br />

2 of 2<br />

Issue 5 May 2009 1413

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

Saved successfully!

Ooh no, something went wrong!