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.

This test is run for ANL-LINE (8-Port Analog Line).<br />

Table 395: Looparound and Conference Test (#47) 1 of 5<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

Looparound and Conference Test (#47)<br />

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

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

7 ABORT The port was seized by a user for a valid call.<br />

1. Enter display port location to determine the station’s<br />

extension.<br />

2. Enter status station extension to determine the service<br />

state of the port. If the port is in use, wait until the port is idle before<br />

retesting.<br />

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

1000 ABORT System resources required to run this test were not available. The port<br />

may be busy with a valid call. This could be a Music-on-Hold port.<br />

1. Enter display port location to determine the station’s<br />

extension.<br />

2. Enter status station extension to determine the service<br />

state of the port. If the port is in use, wait until the port is idle before<br />

retesting.<br />

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

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

be under heavy traffic conditions, or it may have time slots<br />

out-of-service due to TDM-BUS errors. A system is considered under<br />

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

or when the System Management and the Call Processing Occupancies<br />

together exceed 65%.<br />

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

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

errors.<br />

3. If the system has no TDM-BUS errors and is not handling heavy<br />

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

1 of 5<br />

Communication Manager Release 5.0 Issue 4 January 2008 1505

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

Saved successfully!

Ooh no, something went wrong!