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.

Table 40: Error <strong>codes</strong> <strong>and</strong> Aux Data values ATM-NTWK 2 of 6<br />

Cause<br />

Code/<br />

Error<br />

Type<br />

Aux<br />

Data<br />

ATM-NTWK (ATM Network Error)<br />

21 (a) Call rejected. This cause indicates that the equipment sending this cause<br />

does not wish to accept this call, although it could have accepted the call<br />

because the equipment sending this cause is neither busy nor<br />

incompatible.<br />

Note: If the call was rejected by the far-end ATM-EI or ATM-CES board,<br />

there could also be additional information about this rejection in an ATM-EI<br />

<strong>error</strong> log entry. Look for an ATM-EI or <strong>error</strong> with an Error Type between<br />

1104 <strong>and</strong> 1119 inclusive, with approximately the same time stamp as this<br />

<strong>error</strong>.<br />

22 (a) Number changed. This cause is returned to a calling party when the called<br />

party’s number indicated by the calling user is no longer assigned. The new<br />

called party’s number can optionally be included in the diagnostic field. If a<br />

network does not support this capability, cause number 1 “unassigned<br />

(unallocated) number” is used.<br />

23 (a) User rejects every call with CLIR (calling line identification restriction). This<br />

cause is returned by the called party when the call is offered without calling<br />

party’s number information <strong>and</strong> the called party requires this information.<br />

27 (a) Destination out of order. This cause indicates that a user-indicated<br />

destination cot be reached because a signaling message could not be<br />

delivered to the remote user over the destination’s interface (for example, a<br />

physical-layer or SAAL failure at the remote user, or remote user’s<br />

equipment is off line).<br />

28 (a) Invalid number format (address incomplete). This cause indicates that the<br />

called user cot be reached because the called party’s number is not in a<br />

valid format or has insufficient digits.<br />

30 (a) Response to STATUS ENQUIRY. This cause is included in the STATUS<br />

message when the reason for generating the STATUS message was the<br />

prior receipt of a STATUS ENQUIRY message.<br />

31 (a) Normal, unspecified. When no more specific cause values apply, this cause<br />

reports a normal event.<br />

32 (a) DTL transit not-my-node ID<br />

RESOURCE UNAVAILABLE<br />

Cause Codes Description<br />

35 (a) Requested VPCI/VCI not available. This cause indicates that the requested<br />

VPCI/VCI is not available. This can be caused by mismatched VCI ranges<br />

on different ATM switches.<br />

36 (a) VPCI/VCI assignment failure<br />

2 of 6<br />

Issue 5 May 2009 149

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

Saved successfully!

Ooh no, something went wrong!