Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-286CO-DS1 (DS1 CO Trunk)
10
The DS1 Interface circuit pack detected a hardware fault. These errors
cause the Dial Tone Test (#314) to run and are only considered a problem
if the Dial Tone Test fails (in which case Error Type 1025 also shows up).
In this case, the trunk may be put in ready-for-service state (shown as
"disconnected" by status command), which allows only incoming calls.
Run the Dial Tone Test (#314) and follow its outlined procedures.
b. Error Type 15—This is a software audit error that does not indicate any
hardware malfunction. Run Short Test Sequence and investigate
associated errors (if any).
c. Error Type 18—System Technician has busied-out the trunk to the
out-of-service state. No calls can be made on this trunk except the Facility
Access Test Call. For details on this feature, refer to "Facility Test Calls"
section in Chapter 5, "Routine Maintenance Procedures".
d. Error Type 130—This error type indicates that the circuit pack has been
removed or has been insane for more than 11 minutes. To clear the error,
reinsert or replace the circuit pack.
e. Error Type 257—The DS1 Interface circuit pack detects a hardware fault.
The Aux Data field contains the following error type: 57392—no external
release on PBX disconnect [E030]. Escalate the problem.
f. Error Type 513—The DS1 Interface circuit pack detects a hardware fault.
The Aux Data field contains the following error type: 57393—belated
external release on PBX disconnect [E031]. Escalate the problem.
g. Error Type 769—The DS1 Interface circuit pack detects a hardware fault.
The Aux Data field contains the following error type:—57484, fault is
detected on tip/ring [E08C]. Escalate the error.
h. Error Type 1793—DS1 Interface circuit pack is out-of-service. Look for
DS1-BD errors in the Hardware Error Log. Refer to the DS1-BD (DS1 Trunk
Circuit Pack) Maintenance documentation for details.
i. 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.
j. 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 Dial Tone Seizure Test (#314) and follow
those procedures.
k. 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. If the test
continues to abort, then escalate the problem.