¹Minor alarms on this MO may be down graded to Warning alarms based on the value in set options.

Notes:

1. Error type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each test’s description, and follow its procedures.

2. Error type 18: The PMS Link has been busied out with busyout pms-link. The link is torn down. Enter release pms-link to restore the link.

3. Error type 257: The Link Retry test (#215) fails. An error was detected when setting up the link. Refer to the Procedures for Restoring the PMS Link above.

4. Error type 513: The PMS physical link is down for one of the following reasons:

   • Cable to the PMS device is disconnected.

   • The PMS device is powered off.

   • The data extension to which the PMS device connects has been busied out.

   Check the connectivity of wire and cable among wall jacket, data module, and the PMS device. Enter status data extension and verify that the data extension of the PMS device is in the in-service/idle state. If the data extension is not available, then see Procedures for Restoring the PMS Link.

5. 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.

6. 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 Error Log.

7. 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 Error Log.

8. 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 Error Log. No alarm is raised against this error.

9. 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 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.

10. 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 Error Log. No alarm is raised against this error.

11. 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.

12. Error type 2561: The PMS Link is physically established, but the protocol has not been started by the PMS before the protocol timer expires. 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 Error Log. The PMS should be checked to make sure that it will attempt to start the protocol according to the PMS/PBX protocol specifications. No alarm is raised against this error.

13. Error type 2817: Look for the following Aux Data:

    10x	The PMS violated the application protocol. The first message after a request to initiate a database exchange was not the start of a database exchange. The message is processed. If this Error Type with this aux data value 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 Error Log.
    20x	The PMS violated the application protocol. The start of a database exchange was received in a state in which it was not expected. The message is ignored. If this Error Type with this Aux data value 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 Error Log.
    30x	The PMS violated the application protocol. The end of a database exchange was received when no exchange was in progress. The message is ignored. If this Error Type with this Aux Data value 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 Error Log. No alarm is raised against this error.

    The PMS should be assessed for adherence to the PMS/PBX protocol specifications.

14. Error type 3073: The link was taken down by the switch because the threshold for application protocol violations has been exceeded by the PMS. The protocol never started and messages were received and/or messages were received in a state in which they were not expected. Refer to Error Type 2817 for recommended strategy.

15. Error type 3841: Link was taken down by the switch because the threshold for link protocol violations has been exceeded by the PMS. PMS is sending garbage to the switch.