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-296
CO-DS1 (DS1 CO Trunk)
10
DS1 CO Dial Tone Seizure Test (#314)
DS1CO Dial Tone Seizure Test checks the trunk’s signaling capability provided
by the DS1 Interface circuit pack. The maintenance software initiates the test by
sending a "seizure" message to the DS1 Interface circuit pack and expects an
"active" reply from the DS1 interface circuit pack. If the "active" message is
received, then the test passes. If no message is received and the timer expires,
the test is aborted. If the DS1 Interface circuit pack sends a "reorder" message
back to maintenance software, then the test fails.
by the DS1 Interface circuit pack. The maintenance software initiates the test by
sending a "seizure" message to the DS1 Interface circuit pack and expects an
"active" reply from the DS1 interface circuit pack. If the "active" message is
received, then the test passes. If no message is received and the timer expires,
the test is aborted. If the DS1 Interface circuit pack sends a "reorder" message
back to maintenance software, then the test fails.
The test
CANNOT
be run on a trunk if one of the following cases is true:
a. The trunk direction is administered as an incoming only trunk.
b. The trunk has been seized by a normal trunk call.
c. The trunk is administered with maintenance test disabled.
0
NO
BOARD
BOARD
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, an insane board is inserted, or the board is hyperactive
(see note below).
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, an insane board is inserted, or the board is hyperactive
(see note below).
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, dispatch to check to ensure that there is a valid board
inserted.
this is not the case, dispatch to check to ensure that there is a valid board
inserted.
Hyperactivity causes some special problems with the sequence suggested
above. If the ports are translated after issuing the
above. If the ports are translated after issuing the
list config
command but
the ’Vintage’ field reports that there is no board (when there really is a
board), then the
board), then the
busyout board
and the
release busy board
commands
will not work (even though the
reset board
command will work). The
software will put the hyperactive board back in service after the
hyperactivity clears.
hyperactivity clears.
Table 10-97.
TEST #36 Port Audit and Update Test —
Continued
Error
Code
Code
Test
Result
Description/ Recommendation
Continued on next page