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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 26: ASAI cause values 2 of 3<br />

Code Explanation Recommendation<br />

50 Requested<br />

facility not<br />

subscribed<br />

58 Bearer<br />

capability not<br />

currently<br />

available<br />

63 Service or<br />

option not<br />

available<br />

65 Bearer<br />

service not<br />

implemented<br />

ASAI-EPT (ASAI Endpoint)<br />

Requested facility is implemented, but not administered. Potential<br />

administration problem with endpoint or adjunct.<br />

For BRI endpoints:<br />

1. Verify the switch administration of endpoint using display<br />

station or display data-module.<br />

2. If step 1 does not resolve the problem, refer to the endpoint’s<br />

service manual <strong>and</strong> verify administration on the endpoint.<br />

For ASAI adjuncts:<br />

1. Display the Customer Optional Features screen<br />

(administration screen) on the switch to determine which ASAI<br />

capabilities are turned on in the switch.<br />

2. Verify that the adjunct is administered to support the identical<br />

capabilities as the switch. If there is a mismatch in the<br />

administered capabilities, then re-administer the switch <strong>and</strong>/or<br />

the adjunct to establish a consistent set of desired capabilities<br />

on both the switch <strong>and</strong> the adjunct.<br />

Requested bearer capability is implemented, but not administered.<br />

No B-Chel is administered. See code 50 above.<br />

Requested ASAI capability or resource is not available on the switch<br />

or adjunct. More than one adjunct may be contending for the same<br />

switch resource. Potential administration mismatch between the<br />

resource domains administered on the switch <strong>and</strong> those<br />

administered on the adjunct.<br />

1. Verify that no overlapping administration of switch resources<br />

(for example, requesting notifications on a single domain by<br />

multiple adjuncts attempting to control a single call) exists<br />

across any adjunct connected to the switch. If an overlap<br />

exists, then re-administer the adjuncts to ensure that each<br />

adjunct is associated with a unique set of switch resources.<br />

Requested service not implemented in switch or endpoint.<br />

2 of 3<br />

Issue 5 May 2009 109

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

Saved successfully!

Ooh no, something went wrong!