Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1842 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
e. Error Type 769: there has been no communication between the switch and the PMS for a
period of time specified in “system hospitality” administration. The PMS Link is torn down.
To clear this error, see Procedures for Restoring the PMS Link
on page 1840.
f. Error Type 1025: The link was taken down because the switch could not receive an
incoming message from the PMS. The message from the PMS repeatedly had corrupted
data or the switch received requests for acknowledgment but never received a message to
be processed. If this error type occurs frequently (more than once a month), advise the
customer to call the vendor of the PMS to check out the PMS device. Once the PMS Link is
successfully established, this error disappears from the Hardware Error Log.
g. Error Type 1281: the link was taken down because the switch could not send an outgoing
message. The message, which was sent but not acknowledged, was flushed. If this error
type occurs frequently (more than once a month), advise the customer to call the vendor of
the PMS to check out the PMS device. Once the PMS Link is successfully established, this
error disappears from the Hardware Error Log.
h. Error Type 1537: the PMS has been busied out for maintenance at the request of the PMS.
The PMS Link is torn down. The reason code (N), if present, is that supplied by the PMS in
the request message. If this error type recurs frequently (that is, more than once a month),
advise the customer to call the vendor of the PMS to check out the PMS device. Once the
PMS Link is successfully established, this error disappears from the Hardware Error Log.
No alarm is raised against this error.
i. Error Type 1793: due to heavy call traffic, or the PMS protocol message rate being faster
than the PMS/PBX protocol specifications allow, the PMS Link is torn down. PMS Link
maintenance software will wait for five minutes before attempting to set up the link again. If
this error type occurs frequently (more than once a month), advise the customer to call the
vendor of the PMS to check out the PMS device. Once the PMS Link is successfully
established, this error disappears from the Hardware Error Log. The PMS should be
checked for adherence to message rate defined in the PMS/PBX protocol specifications. No
alarm is raised against this error.
j. Error Type 2049: The attempt to swap the database between PBX and PMS failed three
times consecutively due to excessive PMS/PBX protocol violations, buffer overflows, or
PMS Link outages. The PMS Link is NOT torn down. If this error type occurs frequently
(more than once a month), advise the customer to call the vendor of the PMS to check out
the PMS device. Once the PMS Link is successfully established, this error disappears from
the Hardware Error Log. No alarm is raised against this error.
k. Error Type 2305: The PMS Link was busied out with busyout pms-link, or it was
brought down with test pms-link long. The PMS Link is torn down, and PMS Link
maintenance stops attempts to reestablish the link in the case where the busyout
pms-link was used. When test pms-link long has been used, PMS Link
maintenance continues trying to reset the link. To restore the PMS Link after use a
busyout pms-link, enter release pms-link. To restore the PMS Link after a test
pms-link long, enter test pms-link.