Avaya DEFINITY Server CSI Maintenance Manual page 1487

PMS-LINK (Property Management System Link)
l. Error Type 2817:
Aux values of concern:
10x
20x
30x
m. 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.)
n. 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.
555-233-119
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 recurs frequently (that is, more than
once a month), then 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. See Note.
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 recurs frequently (that is, more than once a month),
then 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.
See the next Note.
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 recurs frequently (that is, more than once a month),
then 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.
NOTE:
The PMS should be assessed for adherence to the
PMS/PBX protocol specifications. No alarm is raised
against this error.
Issue 5 October 2002
1487