19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

l. Error Type 2561: the PMS Link is physically established, but the protocol has not been<br />

started by the PMS before the protocol timer expires. The PMS Link is NOT torn down. If<br />

this Error Type occurs frequently (more than once a month), advise the customer to call the<br />

vendor of the PMS to check out the PMS device. Once the PMS Link is successfully<br />

established, this <strong>error</strong> disappears from the Error Log. The PMS should be checked to make<br />

sure that it will attempt to start the protocol according to the PMS/PBX protocol<br />

specifications. No alarm is raised against this <strong>error</strong>.<br />

m. Error Type 2817: look for the following Aux Data:<br />

10x The PMS violated the application protocol. The first message after a request<br />

to initiate a database exchange was not the start of a database exchange.<br />

The message is processed. If this Error Type with this aux data value occurs<br />

frequently (more than once a month), advise the customer to call the vendor<br />

of the PMS to check out the PMS device. Once the PMS Link is successfully<br />

established, this <strong>error</strong> disappears from the Error Log.<br />

20x The PMS violated the application protocol. The start of a database exchange<br />

was received in a state in which it was not expected. The message is ignored.<br />

If this Error Type with this Aux data value occurs frequently (more than once a<br />

month), advise the customer to call the vendor of the PMS to check out the<br />

PMS device. Once the PMS Link is successfully established, this <strong>error</strong><br />

disappears from the Error Log.<br />

30x The PMS violated the application protocol. The end of a database exchange<br />

was received when no exchange was in progress. The message is ignored. If<br />

this Error Type with this Aux Data value occurs frequently (more than once a<br />

month), advise the customer to call the vendor of the PMS to check out the<br />

PMS device. Once the PMS Link is successfully established, this <strong>error</strong><br />

disappears from the Error Log. No alarm is raised against this <strong>error</strong>.<br />

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

n. Error Type 3073: the link was taken down by the switch because the threshold for<br />

application protocol violations has been exceeded by the PMS. The protocol never started<br />

<strong>and</strong> messages were received <strong>and</strong>/or messages were received in a state in which they were<br />

not expected. (Refer to Error Type 2817 for recommended strategy.)<br />

o. Error Type 3841: link was taken down by the switch because the threshold for link protocol<br />

violations has been exceeded by the PMS. PMS is sending “garbage” to the switch.<br />

748 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!