ATM network-generated cause codes

Explanation: The number requested by the calling user cannot be reached because it is not currently assigned to any user by the network.

Explanation: The equipment issuing this cause received a request to route the call through a transit network that it does not recognize. The equipment issuing this cause does not recognize the transit network because the network does not exist, or the network exists but does not serve the equipment that is sending this cause. This message is network dependent.

Explanation: The called user cannot be reached because the network that serves the called user is inaccessible.

Explanation: The call is being cleared because one of the users involved in the call has requested that the call be cleared.

Explanation: The called user has indicated an inability to accept another call, although the called user equipment is compatible with the call.

Explanation: The user did not respond to a call establishment message with a connect indication within the time allocated.

Explanation: The called user did not accept this call, although it could have been accepted because the called user was neither busy nor incompatible.

Explanation: The called party number indicated by the calling user is no longer assigned.

New destination is formatted as the called party number information element, including the information element identifier. Transit network selection might also be included.

Explanation: The user rejects all calls with calling line identification restriction (CLIR).

Explanation: The user has not been routed the incoming call.

Explanation: The destination cannot be reached because a signaling message could not be delivered to the called user.

Explanation: The called user cannot be reached because the called party number is not a valid format or is not complete.

Explanation: This value is included in the status message after the prior receipt of a status inquiry message.

Explanation: A normal event occurred and no other cause in the normal event class applies.

Explanation: The network is not functioning correctly, and the condition is likely to last a long time. Immediately trying a call again is not likely to be successful.

Explanation: The network is not functioning correctly, but the condition is not likely to last a long time. Another call attempt can be tried almost immediately.

Explanation: The network could not deliver access information to the called user as requested. Access information includes low-layer compatibility and high-layer information.

Multiple information element identifiers might be included.

Explanation: A resource unavailable event occurred and no other cause in the resource unavailable class applies.

Explanation: The requested quality of service cannot be provided.

Multiple ATM user cell rate subfield identifiers might be included.

Explanation: The requested bearer service is implemented by the equipment, but it is not available at this time.

Explanation: A service or option is unavailable and no other cause in the service or option-not-available class applies.

Explanation: The equipment issuing this cause does not support the requested bearer capability.

Explanation: A service or option is not implemented and no other cause in the service or option-not-implemented class applies.

Explanation: The equipment sending the cause received a message with a call reference that is not currently in use on the user-network interface.

Explanation: The equipment issuing this cause received a request to establish a call that has low-layer compatibility, high-layer compatibility, or other compatibility attributes that it cannot accommodate.

Explanation: The equipment issuing this cause received a request to establish a call that has low-layer compatibility, high-layer compatibility, or other compatibility attributes that it cannot accommodate.

Multiple information element identifiers might be included.

Explanation: An incorrectly formatted transit network identifier was received.

Explanation: A message event occurred and no other cause in the incorrect message class applies.

Explanation: The equipment sending this cause received a message that is missing an information element required to process the message.

Multiple information element identifiers might be included.

Explanation: The equipment sending this cause received a message that it does not recognize because the message is not defined or it is defined but not implemented by the equipment sending the cause.

Explanation: The equipment sending this cause received a message that included an information element that is not recognized because the identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the equipment issuing the cause does not require the information element to be present in the message for processing.

Multiple information element identifiers might be included.

Explanation: The equipment sending this cause received an information element that it has implemented, but one or more of the parameters in the information element are coded incorrectly or not implemented.

Multiple information element identifiers might be included.

Explanation: A message has been received that is incompatible with the call state.

Explanation: A procedure has been initiated by the expiration of a time in association with Q.2931 error handling procedures.

Explanation: A protocol error event occurred and no other cause in the protocol error class applies.

Explanation: Interworking occurred with a network that does not provide causes for actions that it takes. The precise cause for a message that is being sent cannot be ascertained.