Avaya DEFINITY Server CSI Maintenance Manual page 1703

TIE-TRK (Tie Trunk)
Loop Around and Conference Circuit Test (#33)
This test checks the reflective loop around, and conference capabilities of a tie
trunk port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. This is an
on-board test only, and each tone is transmitted through the loop and checked
upon return.
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 the trunk administration Test field.
Table 502. TEST #33 Loop Around and Conference Circuit Test
Error Test
Code Result
ABORT
7 ABORT
129 ABORT
131
133
1000 ABORT
555-233-119
Description/ Recommendation
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 a maximum of 5 times.
The conference circuit test was aborted.
1. Retry the command at 1-minute intervals a maximum of 5 times.
The 404-Hz reflective loop around test aborted. Response to the test
request was not received within the allowable time period.
The 1004-Hz reflective loop around test aborted. Response to the test
request was not received within the allowable time period.
The 2804-Hz reflective loop around test aborted. Response to the test
request was not received within the allowable time period.
1. Retry the command at 1-minute intervals for a maximum of 5 times.
System resources required to run this test are not available. The trunk may
be busy with a valid call. Use the display trunk xx command to determine
the trunk group/member number of the port. Use the status trunk
command to determine the service state of the port. If the service state
indicates that the port is in use, the port is unavailable for certain tests. You
must wait until the port is idle before retesting.
1. If the port status is active, but the port is not in use (no calls), check the
Error Log for Error Type 1025 (see Error Log table for a description of
this error and required actions). The port may be locked up.
2. If the port status is idle, retry the command at 1-minute intervals a
maximum of 5 times.
Continued on next page
Issue 5 October 2002
1703