Filter
Top Products
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-596test inads-link
8
line. The line must be free so the system can place a call to INADS. A local SAT
user entering the "test inads-link" command need not log off for the system to
place a call to INADS, but the two minute delay still exists.
Once the call is answered by INADS, the system will send a message with a test
alarm type. INADS acknowledges receipt of the message and creates a trouble
ticket. The trouble ticket will be closed immediately and have a "INADS LINK
TEST" message entered in the description field. If an alarm is raised while the test
call is up, the system will not send an alarm message over the existing link. The
normal retry mechanism will be followed, which means an attempt to make a call
to INADS to report the error will take place seven (7) minutes later. An INADS
trouble ticket will be created only if the connection is successfully established,
and a message is sent to the system acknowledging that INADS received the
system message.
The "Maintain Process Circuit Packs" field must be set to yes on the inads and
technician permission forms. This will provide permissions to execute the "test
inads-link" command. The field can be changed by executing a "change
permission login" command.
There will be no alarms raised on the system as a result of the "test inads-link"
command. Attendant alarm and acknowledgment lamp states will not be
changed as a result of the command. The test will not be run during periodic or
scheduled maintenance.
Defaults
The test will default to test the link to the first OSS telephone number.
Parameter
Help Messages
If the system technician presses HELP after entering "test inads-link" the following
message will be displayed:
[‘1’ or ‘2’]
Or press CANCEL to cancel the command
If the command entered is in conflict with another currently executing command,
then a message will be displayed showing the login id of the conflicting user and
the conflicting command. The message is as follows:
’login id’:’command’ has a command conflict
1 This option causes testing of the link to the first OSS telephone number.
2 This option causes testing of the link to the second OSS telephone number.