Lucent Technologies R5SI User Manual
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-348
CO-TRK (CO Trunk)
10
Loop Around and Conference Circuit Test (#33)
This test checks the reflective loop around and conference capabilities of a CO
port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. Each tone is
transmitted separately through the loop and checked.
port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. Each tone is
transmitted separately through the loop and checked.
Table 10-97.
TEST #33 Loop Around and
Conference Circuit Test
Error
Code
Test
Result
Description/ Recommendation
ABORT
Could not allocate the necessary system resources to run
this test.
this test.
7
ABORT
Conference Circuit Test aborted.
129
ABORT
The 404-Hz reflective loop around test aborted. Response to
the test request was not received within the allowable time
period.
the test request was not received within the allowable time
period.
131
The 1004-Hz reflective loop around test aborted. Response
to the test request was not received within the allowable time
period.
to the test request was not received within the allowable time
period.
133
The 2804-Hz reflective loop around test aborted. Response
to the test request was not received within the allowable time
period.
to the test request was not received within the allowable time
period.
1. Retry the command at 1 minute intervals a maximum of 5
times.
2. If 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. Use the
The port may be busy with a valid call. Use the
display port
UUCSSpp
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, then the port is unavailable
for certain tests. You must wait until the port is idle before
retesting.
indicates that the port is in use, then 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 769 (see the
Error Log table for a description of this error and
required actions). The port may be locked up.
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 for a maximum of 5 times.
3. If the test continues to abort, escalate the problem.
Continued on next page