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.

Communication Manager Maintenance Object Repair Procedures<br />

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

Table 40: Error <strong>codes</strong> <strong>and</strong> 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 />

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

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

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 cot 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 chel 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 />

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

1 of 6

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

Saved successfully!

Ooh no, something went wrong!