Lucent Technologies lucent ユーザーズマニュアル
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-467
DIOD-TRK (DIOD Trunk) [G1.2SE]
10
For example, you may also clear errors generated from other tests in the testing
sequence.
sequence.
Dial Tone Test (#0)
This test attempts to seize a port and checks for the return of a dial tone.
1.
D = Destructive; ND = Nondestructive
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND
1
NPE Crosstalk Test (#6)
X
ND
Dial Tone Test (#0)
X
ND
Loop Around and Conference Test (#33)
X
ND
Audit Update Test (#36)
X
X
ND
Table 10-155.
TEST #0 Dial Tone Test
Error
Code
Code
Test
Result
Description/ Recommendation
ABORT
Could not allocate system resources to run this test.
1. Retry the command at one-minute intervals a maximum of five times.
2. 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. Use the command
be busy with a valid call. Use the command
display port PCSSpp
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. (Refer to the "Status Commands" section in Chapter 10,
"Maintenance Commands and Trouble-Clearing Aids" for a full description
of all possible states.) You must wait until the port is idle before retesting.
tests. (Refer to the "Status Commands" section in Chapter 10,
"Maintenance Commands and Trouble-Clearing Aids" for a full description
of all possible states.) You must wait until the port is idle before retesting.
1. If the port status is idle, then retry the command at one-minute
intervals a maximum of five times.
2. If the test continues to abort, escalate the problem.
1001
ABORT
Could not allocate the necessary system resources to run this test.
1. Retry the command at one-minute intervals a maximum of five times.
2. If the test continues to abort, escalate the problem.
Continued on next page