Avaya S8700 - Page 1244

Maintenance-Object Repair Procedures
555-233-143
8-522 Issue 1 May 2002
Looparound and Conference Circuit Test (#33)
This test checks the reflective and non-reflective loop around and conference
capabilities of a DID port circuit. The test that uses 404-, 1004-, and 2804-Hz
tones is an on-board test only. Each tone is separately transmitted to and from
the port (loop around within the port) and verified.
This test may fail due to noise induced by adjacent electric power lines.
Customers having this problem should resolve it with their local power company.
To temporarily alleviate the alarm caused by the failure of this test, the test may be
disabled from trunk administration Test field. (This also disables the port
diagnostic test.)
Table 8-210. Test #33 Loop-Around and Conference Circuit Test
Error
Code
Te s t
Result Description / Recommendation
ABORT Could not allocate the necessary system resources to run this test. This could
be due to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
3 ABORT System resources required to run this test are not available. The seized tone
detector did not respond. This abort code is usually associated with
tone-clock (TONE-BD, TONE-PT, and TDM-CLK) resources.
1. Clear any tone errors in the error log.
2. Retry the command a 1-minute intervals up to 5 times.
3. If the test continues to abort, escalate the problem.
1000 ABORT System resources required to run this test are not available. The port may be
busy with a valid call.
1. Enter display port UUCSSpp to determine the station extension,
attendant number, or trunk group/member number of the port. Use
status station, status attendant, or status trunk to determine the
service state of the port. If the port is in use, wait until it is idle before
testing. Attendants are always in use (off-hook) if the handset is plugged
in and the port is not busied out.
2. If the port status is active but the port is idle (no calls), check the Error
Log for Error Type 513. The port may be locked up.
3. If the port status is idle, retry the command at 1-minute intervals up to 5
times.
Continued on next page