Avaya G700 Maintenance Manual page 247

6 Avaya MultiVantage Software-Controlled Maintenance:
• (c) Error Type 18—The DS1 tie trunk has been busied out by a busyout trunk grp/mbr
command. No calls can be made on this trunk except for the Facility Access Test Call. Facility
Access Test Calls are described in Chapter 6 and in Administrator's Guide for Avaya
MultiVantage™ Software, 555-233-506.
• (d) Error Type 19—This error type indicates that the far-end may be out-of-service, or the
Electronic Tandem Network may be busied out.
• (e) 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.
• (f) Error Type 257—The DS1 Interface Media Module detects a hardware error on the DS1 tie
trunk. The trunk cannot
communicate with the far end because it is unable to interpret digits sent from the far-end switch.
The Aux Data field indicates the following:
Check with the far-end switch or operating company for proper trunk connection.
• (g) Error Type 513— DS1 Interface Media Module detects a hardware error on the DS1 tie trunk.
The trunk is in-service/active and waiting for an "on-hook" from the far-end switch. No calls can
be routed over the trunk while it is in this state. Aux Data 57392 indicates no external release on
PBX disconnect. Check with the far-end switch or operating company for proper trunk connection.
• (h) Error Type 769—The DS1 Interface Media Module detects a hardware error on the DS1 tie
trunk. This error usually occurs after an occurrence of error type 513. The trunk has received the
belated "on-hook" that it has been waiting for from the far-end switch. The trunk is restored to in-
service/idle and can be used for calls. Aux Data 57393 indicates delayed external release on PBX
disconnect. This error can be ignored.
• (i) Error Type 1793—The DS1 Interface Media Module is out-of-service. See MG-DS1
Maintenance documentation for details.
• (j) Error Type 2305—Reorder message. The trunk could not be seized. This error causes the Trunk
Seizure Test (#136) to run and is only a problem if the Seizure Test fails (in which case Error Type
1025 also appears). In this case, the trunk may be put in ''Ready-for-Service'' state (shown as
''disconnected'' by the status command), which allows only incoming calls. Run the Trunk Seizure
Test (#136) and follow its procedures.
• (k) 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.
• (l) 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 DS1 Tie Trunk Seizure Test (#136) and follow its outlined procedures.
• (m) Error Type 3840—Port Audit and Update Test (#36) failed due to an internal system error.
Enter status trunk command and verify the status of the trunk. If the trunk is out-of-service, then
enter release trunk command to put it back to in-service. Retry the test command.
Maintenance for S8300/S8700 and G700
555-234-101 — Issue 2 — October 2002
57473 The rotary dial rate is below 8 pulses per second.
57474 The rotary dial rate is above 12 pulses per second.
TIE-DS1 (DS1 Tie Trunk)
247