Lucent Technologies R5SI Computer Hardware User Manual


  Open as PDF
of 2643
 
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-478DIG-LINE (Digital Line)
10
If the primary information channel test is successful, the loop around test for the
secondary information (data, Information Channel 2 or I2) channel is then
performed. This test is the same as the primary information channel loop around
test and is performed only if a DTDM is administered, which is also the case for a
linked DA.
Only one value (Pass. Fail, or Abort) is generated as a result of the two tests run.
If any test fails aborts, the sequence is stopped. Upon completion of this test the
associated endpoint and port are moved back into the previous service state.
Table 10-129. TEST #1201 Digital Terminal Remote
Loop Around Test
Error
Code
Test
Result Description/ Recommendation
ABORT Internal System Error
1. Retry the command at 1-minute intervals a maximum
of 5 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 display portUUCSSpp/PCSSpp command to
determine the station extension or attendant number of
the port. Use status station or status attendant 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 test. (See 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 re-testing. Attendants are
always in use (off-hook) if the handset is plugged in and
the port is not busied out.
1. If the port status is idle, then retry the command at
1-minute intervals a maximum of 5 times.
2. If the test continues to abort, escalate the problem.
1001 ABORT System resources required to run this test are not
available.
1. If the port status is idle, then retry the command at
1-minute intervals a maximum of 5 times.
2. If the test continues to abort, escalate the problem.
Continued on next page