Avaya G350 Maintenance Manual page 95

Notes:
•
In-line errors that have no specific test associated with them. Refer to the following table for an
explanation and appropriate action.
•
A software audit error that does not indicate any hardware malfunction. Run Short Test Sequence
and investigate associated errors.
•
Indicates that the Media Module has been removed or has been insane for at least 11-minutes. To
clear the error, reinsert or replace the Media Module.
•
Aux data 57345 - Single polarity ringing current
Aux data 57376 - No loop current on incoming call
Aux data 57408 - No tip ground detected on outgoing call
Aux data 57424 - No loop current on outgoing call
Aux data 57484 - No dial tone on outgoing call
These errors cause the Dial Tone Test (#0) to run and are only considered a problem if the Dial
Tone Test fails (in which case Error Type 1537 will also show 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 (#0) and follow its outlined procedures.
If error count associated with this error type is very high (i.e., 225) and if Alarm Status on the
Hardware Error Report is n (not alarmed), then the existence of this error type indicates that,
despite the fact that many in-line error messages have been received, all Call Seizure Tests have
passed. Problems at the CO may cause this condition rather than problems with the PBX.
•
If test fails after two repetitions, replace Media Module.
Maintenance of the Avaya G350 Media Gateway
June 2004
Avaya Communication Manager controlled maintenance
CO-TRK (Analog CO Trunk)
95