Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
l. Error Type 513, Aux Data -57392: Loop current active, CO is not releasing trunk after PBX
disconnect. Occurs when the PBX end drops first and the CO does not release the trunk
within 4 minutes.
1. Verify the interface to the network with a hand telephone set. If calls are placed correctly,
then refer problem to the CO.
2. If unable to place calls or this equipment is not available, check the status on port using
status trunk. If active but not connected, disconnect bridging clips at the network
interface. Check status on the trunk. If trunk went idle, then replace clips. If trunk is still
active but unable to place calls, refer problem to the CO.
m. Error Type 513, Aux Data 57393: Late CO trunk release occurs only after the occurrence
of Error Type 513. The CO released the trunk 4 minutes after the PBX dropped the call. This
event decrements the severity (error count) of Error Type 513, or may mean the problem
related to Error Type 513 has been fixed.
Verify that Error Type 513 does not occur again. Refer to Error 513.
n. Error Type 1793: Incomplete Dial timer expired. Applies only to the TN459 and indicates a
problem with incoming dialing stream. Refer the problem to the CO.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation Short Test
Sequence
1. D = Destructive; ND = Nondestructive
Long Test
Sequence
686 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
D/ND 1
NPE Crosstalk Test (#6) X ND
Port Diagnostic Test (#35) X X ND
Looparound and Conference Test (#33) X ND
Port Audit And Update Test (#36) X X ND