09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

Denial Events<br />

Cause Value 16<br />

[0x10/0x90] -<br />

Normal call clearing/<br />

Requested facility not implemented (1TR6: AT&T ISDN Protocol)<br />

Cause Value 16 indicates that the call was disconnected normally by either end hanging up.<br />

Cause Value 16 (1TR6) indicates that the call could not be completed because the equipment<br />

sending this Cause Value does not support the requested service, feature, or supplementary<br />

service in the SETUP message.<br />

This Cause Value has end-to-end significance and should always be passed back through the<br />

network to the user.<br />

Troubleshooting<br />

● Check the diagnostic information (DIAG) for the facility identifier of the not implemented<br />

service. See Cause Values and their meanings/interpretations on page 151.<br />

Cause Value 17<br />

● If the remote device terminated the connection unexpectedly, contact the person<br />

responsible for the remote end to determine if there is a problem with the remote endpoint.<br />

● For data bearer capability calls, if the connection has failed to establish, but the CONNECT<br />

and CONNECT_ACK messages were exchanged before the DISCONNECT was<br />

received, the handshake between the devices involved in the call might have failed due to:<br />

- Option settings with the endpoint devices<br />

- Bandwidth constriction issues on the B-Channels used by the two devices to make the<br />

call<br />

[0x11/0x91] -<br />

User busy/<br />

Requested facility not subscribed (1TR6: AT&T ISDN Protocol)<br />

Cause Value 17 indicates that the endpoint called is unable to accept another call.<br />

Cause Value 17 (1TR6) indicates that the call could not be completed because the user has not<br />

subscribed to the service, feature, or supplementary service requested in the SETUP message.<br />

This Cause Value has end-to-end significance and should always be passed back through the<br />

network to the user.<br />

See also Cause Value 16 on page 164 and Cause Value 31 on page 169.<br />

Troubleshooting<br />

● Wait and try the call again later.<br />

● If the user is supposed to have access to the service, feature, or supplementary service,<br />

complete the ordering process with the ISDN service provider.<br />

164 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

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

Saved successfully!

Ooh no, something went wrong!