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.

Communication Manager Maintenance Object Repair Procedures<br />

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

Code Explanation Recommendation<br />

0 Unrecognized<br />

ASAI Protocol<br />

Operation.<br />

34 No circuit or<br />

chel available<br />

40 Resources<br />

not available.<br />

Requested ASAI protocol is not implemented by switch or adjunct.<br />

Aux Data field of <strong>error</strong> log entry contains protocol identifier for<br />

unrecognized operation.<br />

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

set of operations is supported by switch <strong>and</strong> the adjunct.<br />

Turning off adjunct operations not implemented by the switch<br />

may resolve the problem.<br />

A resource on the switch is unavailable for a call. For BRI endpoints,<br />

this cause value is not logged. For ASAI, this condition means that<br />

there are no available trunks for an outgoing call request.<br />

1. Verify that the adjunct is administered to support the trunk<br />

capabilities of the switch.<br />

2. Investigate trunk-group status by entering status trunk<br />

from the SAT or by requesting trunk-group queries from the<br />

adjunct.<br />

3. Perform trunk diagnostic procedures such as <strong>test</strong> trunk.<br />

No available internal resources to service switch or adjunct request.<br />

Exceeds system transaction capacity for adjunct or switch.<br />

1. May require re-engineering of adjunct services.<br />

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

1 of 3

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

Saved successfully!

Ooh no, something went wrong!