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.

If ATM-NTWK receives more than 6 errors, the most recent are discarded.<br />

Table 136: Error codes and Aux Data values ATM-NTWK 1 of 6<br />

Cause<br />

Code/<br />

Error<br />

Type<br />

Aux<br />

Data<br />

NORMAL EVENTS<br />

Cause Codes Description<br />

0 (a) Network unreachable<br />

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

1 (a) Unallocated (unassigned) number. This cause indicates that the called<br />

party cannot be reached because, although the number is in a valid format,<br />

it is not currently assigned (allocated).<br />

2 (a) No route to specified transit network. This cause indicates that the<br />

equipment sending this cause has received a request to route the call<br />

through a particular network that it does not recognize, either because the<br />

transit network does not exist or because that particular transit network<br />

does not serve the equipment that is sending this cause. This cause is<br />

supported on a network-dependent basis.<br />

3 (a) No route to destination. This cause indicates that the called party cannot be<br />

reached because the network through which the call has been routed does<br />

not serve the destination desired. This cause is supported on a<br />

network-dependent basis.<br />

10 (a) VPCI/VCI unacceptable. This cause indicates that the virtual channel most<br />

recently identified is not acceptable to the sending entity for use in this call.<br />

16 (a) Normal call clearing. This cause indicates that the call is being cleared<br />

because one of the users involved in the call has requested that the call be<br />

cleared. Under normal situations, the source of this cause is not the<br />

network.<br />

17 (a) User busy. This cause indicates that the called party is unable to accept<br />

another call because the user busy condition has been encountered. This<br />

cause value can be generated by the called user or by the network.<br />

18 (a) No user responding. This cause is used when a called party does not<br />

respond to a call establishment message with a connect indication within<br />

the prescribed period of time allocated.<br />

1 of 6<br />

Communication Manager Release 5.0 Issue 4 January 2008 525

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

Saved successfully!

Ooh no, something went wrong!