09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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 122: ASAI cause values 2 of 2<br />

Code Explanation Recommendation<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 />

69 Requested<br />

facility not<br />

implemented<br />

79 Service or<br />

option not<br />

implemented<br />

ASAI-EPT (ASAI Endpoint)<br />

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

No B-Channel 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 and those<br />

administered on the adjunct.<br />

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

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

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

adjunct connected to the switch. If an overlap exists, then<br />

re-administer the adjuncts to ensure that each adjunct is<br />

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

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

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

1. Consult switch and endpoint documentation to determine<br />

service support.<br />

Requested service or option (or combination of selected options) is<br />

not supported (implemented) in switch or the adjunct.<br />

1. Consult switch and adjunct documentation to determine ASAI<br />

service and options supported by both switch and adjunct.<br />

Re-administration of the switch-administered capabilities (see<br />

Customer Optional Feature screen) or those of the adjunct may<br />

be necessary to correct the problem.<br />

81 Invalid CRV An invalid CRV was sent by the adjunct.<br />

1. This may indicate a CRV inconsistency between the switch and<br />

the adjunct. See the CallVisor protocol reference manual.<br />

87 Internal switch<br />

audit<br />

There is an inconsistency in switch data records.<br />

1. There is no action needed, since the switch has corrected the<br />

data inconsistency.<br />

2 of 2<br />

Communication Manager Release 5.0 Issue 4 January 2008 487

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

Saved successfully!

Ooh no, something went wrong!