Avaya S8700 Maintenance Manual page 1287

For multi-connect configurations

Hide thumbs Also See for S8700:

Table of Contents

DIOD-DS1 (DS1 DIOD Trunk)

The DS1 interface circuit pack detects a hardware error on the DS1 DIOD

trunk. The trunk cannot communicate with the far end because it is unable

to interpret digits sent from the far-end switch. Check with the far-end

switch or Operating Company for proper trunk connection.

k. Error Type 2305—Recorder message, trunk could not be seized (Aux

Data 50944). Run Test #314, and follow the outlined procedures.

l. Error Type 2562—Retry Failure error. This error is logged only. It is not a

hardware failure and hence does not start any testing or generate any

alarms. This error comes from Avaya MultiVantage ™ software and is

generated when a second attempt (retry) to seize an outgoing trunk fails.

m. Error Type 2817—Glare error. This error is logged only. It is not a

hardware failure and hence does not start any testing or generate any

alarms. This error is the result of a simultaneous seizure of a 2-way trunk

from both the near and far ends. Attempt to place the call again. If the

error persists, execute the Dial Tone Seizure test (#314), and follow those

n. Error Type 3840—Port Audit and Update test (#36) failed due to an

internal system error. Enter the status trunk command to verify the status

of the trunk. If the trunk is out-of-service, then enter the release trunk

command to put it back into in-service. Retry the test command.

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order they are presented in the table below. By

clearing error codes associated with the NPE Crosstalk test, for example, you

may also clear errors generated from other tests in the testing sequence.

Table 8-227. System Technician-Demanded Tests: DS1-BD

Order of Investigation

NPE Crosstalk test (#6)

Conference Circuit test (#7)

DS1 Dial Tone test (#314)

Port Audit and Update test (#36)

D = Destructive, ND = Nondestructive

Issue 1 May 2002

Troubleshooting