Avaya Definity SI, Maintenance Manual, Page: 1699 / 2968

INADS (INADS Link)
Issue 4 May 2002 10-913 555-233-123
INADS Link Test (no test number)
The INADS Link Test attempts to place a call to INADS (in the background) to
verify the communications link to INADS. When the test inads-link command is
entered, the user immediately sees either “Command successfully completed” or
“Command failed.” The “Command failed” message appears when a previously
run command is entered, the user immediately sees either “Command
successfully completed” or “Command failed” The “Command failed” message
appears when a previously run test inads-link command is in progress or the
system has active alarms which must be reported to INADS. The “Command
successfully completed” means the switch will start the attempt to call INADS in
two minutes (the test still runs even if Alarm Origination is disabled). The
two-minute delay allows a remote INADS technician time enough to hang up the
call and thus free up the INADS line so that the switch can call INADS back. As
error conditions are encountered, errors are logged against INADS. Error codes 1
through 9 can be logged if the test result was “Command successfully completed”
and Error Codes 10 and 11 can be logged if the test result was “Command failed.”
An error is also logged against INADS if the call to INADS finally succeeds. The
INADS software (release 3.2 or later) recognizes this special “test inads” type of
alarm and automatically opens and then closes a trouble ticket which indicates
that the reason for the trouble ticket is a command is in progress or the system
has active alarms which must be reported to INADS. The “Command successfully
completed” means the switch will start the attempt to call INADS in two minutes
(the test still runs even if Alarm Origination is disabled). The two-minute delay
allows a remote INADS technician time enough to hang up the call and thus free
up the INADS line so that the switch can call INADS back. As error conditions are
encountered, errors are logged against INADS. Error codes 1 through 9 can be
logged if the test result was “Command successfully completed” and Error Codes
10 and 11 can be logged if the test result was “Command failed.” An error is also
logged against INADS if the call to INADS finally succeeds. The INADS software
(release 3.2 or later) recognizes this special “test inads” type of alarm and
automatically opens and then closes a trouble ticket which indicates that the
reason for the trouble ticket is a test inads-link command. The trouble ticket
alarm contains a TESTING INADS LINK description field.
After entering the command, it may take as long a nine minutes for the switch to
place the call and for INADS to respond. The Error Log should be examined (use
the category inads) 10 minutes after successfully entering the command to
determine if the call was successful.
Use the following table to interpret the Error Log entries.