Demand test descriptions and error codes - Avaya Support

DID Trunk Testing
The system uses technician-invoked tests of on-board circuitry to diagnose the health of the
trunk. These are described in the following sections. Additionally, inline testing which can
generate errors, is performed while a call is in progress. See the Error Log table for a
description of these errors. These errors may be reproduced by placing a call on the trunk and
checking the error log.
Problems detected during signaling may be caused by off-board faults in the CO switch or
connections for which a Warning alarm is raised.
Before a maintenance test can be run on a port, the port must be idle. If an incoming call seizes
a port that is being tested, the test will abort and the incoming call will proceed.
Ports Out-of-Service without Errors or Alarms
A common trouble on DID trunks that produces no errors or alarms occurs when the CO busies
out (disconnects) the port. This situation occurs when the CO thinks there are problems with the
DID port. In this case, no incoming calls will be possible through this port. This may result in
complaints from outside callers trying unsuccessfully to call in. This problem can be diagnosed
by listing measurements on lightly used trunks. If a particular port is detected as idle, a call to
the CO will be necessary to get the connection back in service.
Error log entries and recommended actions
Table 82: DID-TRK Error Log Entries 1 of 2
Error
Type
Aux
Data
Associated
Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a) 0 Any Any Any test port location
1 (b) Any WRN OFF
1 (c) 57476 WRN OFF
1 (d) 57477 WRN OFF
1 (e) 57483 WRN OFF
15 (f) Any Port Audit and
Update (#36)
310 Maintenance Alarms for Communication Manager, Media Gateways and Servers
1 of 2