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-1455TIE-TRK (Tie Trunk)
10
a. ATMS test are not part of either sequence. They are run either on demand
with the test analog-testcall command or via the ATMS schedule.
NPE Crosstalk Test (#6)
One or more NPE reside on each circuit pack with a TDM Bus interface. The NPE
controls port connectivity and gain, and provides conferencing functions on a
per port basis. The NPE Crosstalk Test verifies that this port’s NPE channel talks
on the selected time slot and never crosses over to time slots reserved for other
connections. If the NPE is not working correctly, one-way and noisy connections
may be observed. This test is usually only part of a port’s Long Test Sequence
and takes 20 to 30 seconds to complete.
Table 10-442. TEST #6 NPE Crosstalk Test
Error
Code
Test
Result Description/ Recommendation
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.
1000 ABORT 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. (Refer to "Status
Commands" section in Chapter 8, ‘‘
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 active, but the port is not in use
(no connected ports), check the Error Log for Error
Type 1025 (see Error Log table for description of this
error and required actions). The port may be locked
up.
2. If the port status is idle, retry the command at
one-minute intervals a maximum of five times.
3. If the test continues to abort, escalate the problem.
Continued on next page