Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
c. Error Type 1: rotary dial before wink. This occurs when the far-end PBX starts dialing
before the PBX sends the wink on a wink-start or delay-dial trunk. Check the far-end PBX to
ensure a translation match at both ends. This error does not apply to TN497.
d. Error Type 1: rotary dial too early. This occurs when the far-end PBX starts dialing too soon
(about 50ms) after seizure on a wink start or delay dial line. Check the far-end PBX to
ensure a translation match at both ends. This error does not apply to TN497.
e. Error Type 1: on-hook before wink. This occurs when the far end goes on-hook before a
wink. Check the far-end PBX to ensure a translation match at both ends. This error applies
only to TN439.
f. Error Type 1: on an outgoing wink-start or delay-dial trunk, the wink time was too short
(less than 80ms) for a valid signal. Check the far-end PBX to ensure a translation match at
both ends. This error does not apply to TN497.
g. Error Type 15: this is a software audit error that does not indicate any hardware
malfunction. Run the short test sequence, and investigate associated errors (if any).
h. Error Type 18: this indicates that the trunk in question has been busied-out by maintenance
personnel.
i. Error Type 130: 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. TN439 does not alarm this
error. This error does not apply to TN497.
j. Error Type 257: the rotary dial rate was too slow — less than 8 pulses per second. Check
the far-end PBX to ensure a translation match at both ends.
k. Error Type 257: the rotary dial rate was too fast — above 12 pulses per second. Check the
far-end PBX to ensure a translation match at both ends.
l. Error Type 257: the time between digits was too short (less than 300ms). Check the far-end
PBX to ensure a translation match at both ends.
m. Error Types 513, 769, 1281: these errors do not apply to TN439 and TN497.
n. Error Type 1025: this indicates that the trunk is still seized with an incoming call. The
far-end PBX is not releasing the trunk after the call was dropped. Check the far-end PBX for
problems.
Once the trunk is released from the call, the severity of this problem is decreased. If Error
Type 1025 does not appear again, this means that the problem has been corrected. Verify
that Error Type 1025 does not reappear in the Error Log.
o. Error Type 2305: reorder message. The trunk could not be seized. This error causes the
Tie Trunk Seizure test (#73) to run and is considered a problem only if that test fails, logging
error 1793. In this case, the trunk may be placed in the ready-for-service state, allowing only
incoming calls. This service state shows up as disconnected on the Trunk Status screen.
Run the Tie Trunk Seizure Test (#73), and follow recommended procedures.
TN439 logs Aux Data 57424 or 50944. Other circuit packs log 50944. This error is
associated with Tie Trunk Dial Test (#747) for TN439, Tie Trunk Seizure Test (#73) for
TN497, and no test for the others.
1342 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers