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.

Table 289: Local Loop Test (#13) 3 of 9<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

Local Loop Test (#13)<br />

1002 ABORT The system could not allocate time slots for the <strong>test</strong>. The system may be<br />

under heavy traffic conditions, or it may have time slots out-of-service<br />

due to TDM-BUS <strong>error</strong>s. A system is considered under heavy traffic<br />

when the Call Processing Occupancy is greater than 50% or when the<br />

System Management <strong>and</strong> the Call Processing Occupancies together<br />

exceed 65%.<br />

1. Enter status health to view the occupancy measurements.<br />

2. Enter display <strong>error</strong>s <strong>and</strong> resolve any TDM-BUS (TDM Bus)<br />

<strong>error</strong>s.<br />

3. If the system has no TDM-BUS <strong>error</strong>s <strong>and</strong> is not h<strong>and</strong>ling heavy<br />

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

1003 ABORT The system could not allocate a tone receiver for the <strong>test</strong>. The system<br />

may be oversized for the number of Tone Detectors present, or some<br />

Tone Detectors may be out of service.<br />

1. Enter list measurements tone-receiver to see<br />

information regarding the system’s tone receivers.<br />

2. Resolve any TTR-LEV (TTR Level) <strong>error</strong>s.<br />

3. Resolve any TONE-PT (Tone Generator) <strong>error</strong>s.<br />

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

3 of 9<br />

Issue 5 May 2009 1109

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

Saved successfully!

Ooh no, something went wrong!