Filter
Top Products
DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-1093TIE-DS1 (DS1 Tie Trunk)
3
‘‘on-hook’’ that it has been waiting for from the far-end switch. The trunk is
restored to in-service/idle and can be used for calls. Aux Data 57393
indicates delayed external release on PBX disconnect. This error can be
ignored.
h. Error Type 1793—The DS1 Interface circuit pack is out-of-service. See the
appropriate DS1-BD/UDS1-BD (DS1/UDS1 Interface Circuit Pack)
Maintenance documentation for details.
i. Error Type 2305
—
Reorder message. The trunk could not be seized. This
error will cause the Trunk Seizure Test (#136) to run and is only considered
a problem if the Seizure Test fails (in which case Error Type 1025 will also
show up). In this case, the trunk may be put in ‘‘Ready-for-Service’’ state
(shown as ‘‘disconnected’’ by the status command), which allows only
incoming calls. Run the Trunk Seizure Test (#136) and follow its outlined
procedures.
j. 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 call processing and is generated when a
second attempt (retry) to seize an outgoing trunk fails.
k. 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 two-way trunk from both
the near-end and the far-end. Attempt to place the call again. If the error
persists, execute the DS1 Tie Trunk Seizure Test (#136) and follow its
outlined procedures.
l. Error Type 3840
—
Port Audit and Update Test (#36) failed due to an
internal system error. Enter
status trunk
command and verify the status of
the trunk. If the trunk is out-of-service, then enter
release trunk
command
to put it back to in-service. Retry the test command.
System Technician-Demanded Tests: Descriptions
and Error Codes
Always investigate tests in the order presented in Table 3-485 when inspecting
errors in the system. By clearing error codes associated with the
NPE Crosstalk
Te s t
, for example, you may also clear errors generated from other tests in the
testing sequence.