Avaya 03-300430 User Manual
Communication Manager Maintenance-Object Repair Procedures
1780 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
d. Error Type 18: the PRI endpoint port has been busied out by busyout pri-endpoint
extension or busyout port location. No wideband calls can be made to this port,
although wideband calls can still be made to other ports within this PRI endpoint if they are
in service.
in service.
e. Error Type 129: the far-end terminal adapter changed its ISDN service state to
out-of-service or maintenance. This may be a temporary condition due to testing of this port
by the far-end terminal adapter or a hardware problem with the port. Outgoing calls to the
terminal adapter will not be allowed over the port, although calls can still be made to other
ports that are in service within the same PRI endpoint. To investigate the status of the port,
enter status pri-endpoint extension.
by the far-end terminal adapter or a hardware problem with the port. Outgoing calls to the
terminal adapter will not be allowed over the port, although calls can still be made to other
ports that are in service within the same PRI endpoint. To investigate the status of the port,
enter status pri-endpoint extension.
f. 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.
g. Error Types 257, 769: disagreement between this switch and the terminal adapter at the
other end of the connection with regard to the ISDN service state of the PRI endpoint port.
The switch will automatically try to recover by performing a service state audit. Use status
pri-endpoint extension to determine the state of the port.
When running the short test sequence, pay close attention to the results of the Service State
Audit test (#256).
The switch will automatically try to recover by performing a service state audit. Use status
pri-endpoint extension to determine the state of the port.
When running the short test sequence, pay close attention to the results of the Service State
Audit test (#256).
h. Error Type 513: This port is not recognized by the far-end terminal adapter. Investigate the
PRI endpoint administration for both the switch and the terminal adapter, and make sure
they agree.
they agree.
i. Error Type 1281: The Conference Circuit test (#7) failed on this port. See Test #7 for repair
procedures.
j. Error Type 1537: The NPE Crosstalk test (#6) failed on this port. See Test #6 for repair
procedures.
k. Error Type 1793: failure of the UDS1 Interface circuit pack. The results of the Signaling Link
State Check test (#255 in the short sequence) are important.
l. Error Type 3073: Two Service State audit attempts have failed (see Test #256). The port
will not be usable for any outgoing calls to the terminal adapter until the test passes and the
port state is changed to in-service. Incoming calls from the terminal adapter will be accepted
over this port, and other ports in the PRI endpoint can still be used for both incoming and
outgoing calls to and from the terminal adapter.
port state is changed to in-service. Incoming calls from the terminal adapter will be accepted
over this port, and other ports in the PRI endpoint can still be used for both incoming and
outgoing calls to and from the terminal adapter.
m. Error Type 3585: the switch received an ISDN RESTART message for an ISDN port that is
not idle. Because calls are not typically cleared with the RESTART message, this error type
may be associated with a dropped call report from a user.
may be associated with a dropped call report from a user.
The following Aux Data values for Error Type 3585 represent the port’s ISDN call state at
the time the unexpected RESTART request was received from the terminal adapter. This
information can be useful if dropped calls are being reported by users of the PRI endpoint.
Aux Data values that do not appear below can be ignored.
the time the unexpected RESTART request was received from the terminal adapter. This
information can be useful if dropped calls are being reported by users of the PRI endpoint.
Aux Data values that do not appear below can be ignored.