Справочник Пользователя для Lucent Technologies R5SI
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-1441
TIE-DS1 (DS1 Tie Trunk)
10
DS1 Tie Trunk Seizure Test (#136)
The DS1 Tie Trunk Seizure Test is run to verify the trunk’s signaling capability.
The test is composed of two parts. The first part queries the circuit pack for the
following errors: Loss of Signal, Red Alarm, Blue Alarm, Yellow Alarm, and
Hyperactivity Alarm. The second part of the test is performed by sending a
seizure message to the DS1 Interface circuit pack and expecting an active reply
by the DS1 Interface circuit pack. If maintenance software does not receive any
The test is composed of two parts. The first part queries the circuit pack for the
following errors: Loss of Signal, Red Alarm, Blue Alarm, Yellow Alarm, and
Hyperactivity Alarm. The second part of the test is performed by sending a
seizure message to the DS1 Interface circuit pack and expecting an active reply
by the DS1 Interface circuit pack. If maintenance software does not receive any
PASS
Trunk translation has been updated successfully. The
current trunk states kept in the DS1 Interface circuit
pack and switch software are consistent. If the trunk is
busied out, the test does not run, but it does return
PASS. To verify that the trunk is in-service:
current trunk states kept in the DS1 Interface circuit
pack and switch software are consistent. If the trunk is
busied out, the test does not run, but it does return
PASS. To verify that the trunk is in-service:
1. Enter
status trunk
command to verify that the trunk
is in-service. If the trunk is in-service, no further
action is necessary. If the trunk is out-of-service,
continue to Step 2.
action is necessary. If the trunk is out-of-service,
continue to Step 2.
2. Enter
release trunk
command to put trunk back into
in-service.
3. Retry the test command.
0
NO
BOARD
BOARD
The test could not relate the internal ID to the port (no
board). This could be due to incorrect translations, no
board is inserted, an incorrect board is inserted, or an
insane board is inserted.
board). This could be due to incorrect translations, no
board is inserted, an incorrect board is inserted, or an
insane board is inserted.
1. Check to ensure that the board translations are
correct. Use the
list config
command, and resolve
any problems that are found.
2. If the board was found to be correctly inserted in
step 1, issue the
busyout board
command.
3. Issue the
reset board
command.
4. Issue the
release busy board
command.
5. Issue the
test board long
command. This should
re-establish the linkage between the internal ID and
the port. If this is not the case, check to see that
there is a valid board inserted.
the port. If this is not the case, check to see that
there is a valid board inserted.
Table 10-439.
TEST #36 Audit and Update Test —
Continued
Error
Code
Test
Result
Description/ Recommendation
Continued on next page