Avaya Definity SI Maintenance Manual page 1229

CO-TRK (CO Trunk)
Table 10-164. CO Trunk Errors with NO Tests — Continued
Error Aux
Type Data
2817 57360 Ground but no ringing. This error occurs on
an incoming call on a ground-start trunk. If
ringing is not detected within 5 seconds of
the Tip being grounded, the call is still
accepted. If the CO is of the No. 5ESS.
switch type, ringing delays of more than 5
seconds during heavy traffic are fairly
common.
2817 57393 On the TN465, the loop is opening too slowly
after a disconnect. This error indicates an
on-board problem, although the trunk may be
functional. On the TN2138, CO released the
trunk at least 4 minutes after the PBX
dropped the call. This error code is log-only
and causes no other testing to occur. No
alarm is generated.
3073 57376 No loop current on incoming call. The
incoming destination has already answered
and no loop current has been detected. If this
is a hard fault, the dial tone test and all
outgoing calls should also fail.
3329 57408 Trunk error. No Tip ground detected on
outgoing call. This error occurs when an
attempt is made to seize a ground-start CO
trunk for an outgoing call and Tip ground is
not detected or the caller hangs up before
Tip ground is detected.
3585 57424 No loop current on outgoing call. This error
occurs on attempt to seize a loop or
ground-start trunk for an outgoing call. An
error occurs if loop current is not detected or
the caller hangs up before it is detected.
Notes:
1. At the administration terminal, busyout the affected port, and run a Long
Test Sequence. Observe the test results. If any tests fail, refer to the
description of the tests and the associated error codes. Release the port. If
users continue to report troubles, check for other errors and make test calls
to determine whether the problem should be escalated or referred to the
CO.
2. At the administration terminal, busyout the affected port, and run a Long
Test Sequence. If Dial Tone Test #0 passes, ignore this error. Release the
port.
555-233-123
Description and System Action System Technician Action
Check for other errors.
Check for other errors.
Check for other errors.
See Notes 1 and 2 at end of
table.
See Note 3 at end of table.
Continued on next page
Issue 4 May 2002 10-443