Error Log Entries and Test to Clear Values

Error Log Entries and Test to Clear Values

Table 58. CO-DS1 Trunk Error Log Entries
Error Type	Aux Data	Associated Test	Alarm Level	On/Off Board	Test to Clear Value
0*	0	Any	Any	Any	test trunk <grp>/<mbr>
1(a)	57408
1(a)	57487
15(b)	Any	Port Audit and Update Test (#36)
18(c)	0	busyout trunk <grp>/<mbr>	WARNING	OFF	release trunk <grp>/<mbr>
130(d)		None	WARNING	ON	test trunk <grp>/<mbr>
769(g)	57484
1793(h)					test board GGGVSpp l
2562(i))	16665
2817(j)	52992
3840(k)		Port Audit and Update Test (#36)
*Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures.
**Major alarms MO may be downgraded to Warning alarms based on the value used in the set options command.
�

Notes:

(a) Error Type 1--Aux Data 57408--No tip ground is detected on an outgoing call.

Aux Data 57487--PBX could not get "loop close" signal.

(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.
(d) Error Type 130--This error type indicates that the Media Module has been removed or has been insane for more than 11-minutes. To clear the error, reinsert or replace the Media Module.
(g) Error Type 769--The DS1 Interface Media Module detects a hardware fault. The Aux Data field contains the following error type:--57484, fault is detected on tip/ring.
(h) Error Type 1793--DS1 Interface Media Module is out-of-service. Look for MG-DS1 errors in the Hardware Error Log. Refer to the DS1 Trunk Media Module or MG-DS1 Media Module 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, escalate.
(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.