UNSPECIFIED

Issued by the router when none of the other codes match. This cause usually occurs in situations of the same type as Cause 1, Cause 88, and Cause 100

404

UNALLOCATED_NUMBER

This cause indicates that the called party could not be reached because although the called party's number is in a valid format, it is not currently assigned (assigned).

404

NO_ROUTE_TRANSIT_NET

This cause indicates that the equipment sending this cause has received a request to route the call through a specific transit network that it does not recognize. The equipment sending this cause does not recognize the transit network, either because the transit network does not exist or because this particular transit network, although it exists, does not service the equipment that sends this cause.

404

NO_ROUTE_DESTINATION

This cause indicates that the called party could not be reached because the network through which the call was routed does not serve the desired destination. This reason is supported depending on the network.

CHANNEL_UNACCEPTABLE

This cause indicates that the last channel identified is not acceptable for the sending entity to use in this call.

CALL_AWARDED_DELIVERED

The user was presented with an incoming call, and that the incoming call connects to a channel already set up for that user for similar calls (for example, burst mode x.25 virtual calls).

NORMAL_CLEARING

Normal call termination

486

USER_BUSY

The called party cannot accept another call because the user is busy. This reason value can be generated by the called user or the network. In the case where the user is determined to be busy, it is noted that the user equipment is compatible with the call.

408

NO_USER_RESPONSE

The called party does not respond to the call setup message with either a warning or a connection indication for the prescribed allotted time period.

480

NO_ANSWER

This cause is used when the called party has been alerted but does not respond with a call indication within the prescribed time period. Note. This cause is not necessarily generated by Q.931 procedures, but may be generated by internal network timers.

480

SUBSCRIBER_ABSENT

This reason value is used when the mobile station is logged out, radio communication with the mobile station is not established, or if the personal telecommunication user temporarily does not have an address in any user network interface.

603

CALL_REJECTED

This cause indicates that the equipment sending this cause does not want to receive the call, although it could have received the call because the equipment sending this cause is not busy or is incompatible. The network can also generate this cause, indicating that the call was dropped due to a supplementary service restriction. The diagnostic field can contain additional information about the additional service and the reason for the refusal.

410

NUMBER_CHANGED

This reason is returned to the calling party when the called party number specified by the calling party is no longer assigned. The new called party number can optionally be included in the diagnostic field. If the network does not support this reason, reason #: 1, an unassigned (unassigned) number must be used.

410

REDIRECTION_TO_NEW_DESTINATION

This reason is used by the general ISUP mechanism, which can be triggered by a switch deciding that a call should be placed on a different called number. Such an exchange can trigger a redirection mechanism using this reason value to request a previous exchange involved in the call to route the call to a new number.

483

EXCHANGE_ROUTING_ERROR

This cause indicates that the user-specified destination could not be reached because the intermediate switch disconnected the call due to a hop count limit being reached. This cause is generated by the intermediate node, which returns 0 when the hop count is decreased.

502

DESTINATION_OUT_OF_ORDER

This cause indicates that the user-specified destination could not be reached because the destination interface is not working properly. The term "not working correctly" indicates that the signaling message could not be delivered to the remote side; for example, a failure of the physical layer or the data link layer on the remote side or disconnected user equipment.

484

INVALID_NUMBER_FORMAT

This cause indicates that the called party could not be reached because the called party's number is invalid or incomplete.

501

FACILITY_REJECTED

This reason is returned when the additional service requested by the user cannot be provided by the network.

RESPONSE_TO_STATUS_ENQUIRY

This cause is included in the STATUS message when the STATUS message was generated because the STATUS INQUIRY was previously received.

480

NORMAL_UNSPECIFIED

This reason is used to report a normal event only when no other reason in the normal class applies.

503

NORMAL_CIRCUIT_CONGESTION

This cause indicates that there is currently no suitable circuit / channel to handle the call.

503

NETWORK_OUT_OF_ORDER

This cause indicates that the network is not working as expected and that the condition is likely to last for a relatively long period of time, for example, an immediate call retry is unlikely to be successful.

503

NORMAL_TEMPORARY_FAILURE

This reason indicates that the network is not working properly and that this condition is unlikely to last for a long period of time; for example, the user might want to try another call attempt almost immediately.

503

SWITCH_CONGESTION

This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

ACCESS_INFO_DISCARDED

This cause indicates that the network was unable to deliver to the remote user the access information as requested, that is, user-to-user information, low-level compatibility, high-level compatibility, or sub-address as indicated in the diagnostics.

503

REQUESTED_CHAN_UNAVAIL

This reason is returned when the other side of the interface cannot provide the schema or channel specified by the requesting entity.

FACILITY_NOT_SUBSCRIBED

This reason indicates that the user has requested an additional service that is available, but the user is not authorized to use it.

403

OUTGOING_CALL_BARRED

This cause indicates that although the calling party is an outgoing CUG subscriber, outgoing calls are not allowed for that CUG subscriber.

403

INCOMING_CALL_BARRED

This cause indicates that although the called party is a CUG subscriber for an incoming CUG call, incoming calls are not allowed for that CUG subscriber.

403

BEARERCAPABILITY_NOTAUTH

This cause indicates that the user has requested a portability that is being implemented by the hardware that generated the cause, but the user is not authorized to use it.

503

BEARERCAPABILITY_NOTAVAIL

This cause indicates that the user has requested a portability that is being implemented by the hardware that generated the cause, but is not currently available.

SERVICE_UNAVAILABLE

This cause is used to report a service or parameter unavailable event only when no other reason in the service class or parameter unavailable applies.

488

BEARERCAPABILITY_NOTIMPL

This cause indicates that the equipment sending this cause does not support the requested portability.

CHAN_NOT_IMPLEMENTED

This cause indicates that the equipment sending this cause does not support the requested channel type.

501

FACILITY_NOT_IMPLEMENTED

This cause indicates that the equipment sending this cause does not support the requested additional services.

501

SERVICE_NOT_IMPLEMENTED

This cause is used to report an unimplemented service or parameter event only when no other reason in the unimplemented service or parameter class applies.

INVALID_CALL_REFERENCE

This cause indicates that the equipment sending this cause received a message with a call reference that is not currently being used in the user-network interface.

488

INCOMPATIBLE_DESTINATION

This cause indicates that the equipment sending this cause has received a call setup request that has low level compatibility, high level compatibility, or other compatibility attributes (eg, data rate) that cannot be met.

INVALID_MSG_UNSPECIFIED

This reason is used to report an invalid message event only if no other reason in the invalid message class applies.

MANDATORY_IE_MISSING

This cause indicates that the equipment sending this cause received a message that is missing an information element that must be present in the message before the message can be processed.

MESSAGE_TYPE_NONEXIST

This cause indicates that the equipment sending this cause received a message with a message type that it does not recognize because the message is undefined or is defined but not implemented by the equipment sending this cause.

WRONG_MESSAGE

This cause indicates that the equipment sending this cause received a message such that the procedures do not indicate that it is a valid message to receive in a call state, or that a STATUS message was received indicating an inconsistent call state.

IE_NONEXIST

This cause indicates that the equipment sending this cause received a message that includes unrecognized information element (s) / parameter (s) because the information element (s) / parameter name (s) are undefined or defined, but the hardware sending the reason is not implemented. This cause indicates that the information element (s) / parameter (s) have been discarded. However, the information element does not need to be present in the message for the equipment sending the cause to be able to process the message.

INVALID_IE_CONTENTS

This cause indicates that the equipment sending this cause received an information item that it implemented; however, one or more fields in I.E. are coded in a way that was not implemented by the hardware sending this cause.

WRONG_CALL_STATE

This cause indicates that a message was received that is incompatible with the call state.

504

RECOVERY_ON_TIMER_EXPIRE

This cause indicates that the procedure was initiated by the expiration of a timer associated with error procedures. This is often associated with NAT issues. Make sure "NAT Mapping Enable" is enabled in your ATA. If it is not NAT related, sometimes it can be ISP related, make sure another outgoing ISP is not fixing the problem.

MANDATORY_IE_LENGTH_ERROR

This cause indicates that the equipment sending this cause received a message that includes parameters that are not recognized because the parameters are not defined or are not implemented by the equipment sending this cause. The reason indicates that the parameters were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter (s) were sent unchanged.

PROTOCOL_ERROR

This cause is used to report a protocol error event only when no other reason in the protocol error class applies.

INTERWORKING

This cause indicates that the interworking call (usually a SW56 service call) has ended.

MANAGER_REQUEST

This reason is used when you send the api command to make it complete the call.

PICKED_OFF

This reason means that the call was picked up from a different extension.

USER_NOT_REGISTERED

This means that you tried to call a SIP user who was not registered.

GATEWAY_DOWN

Gateway not working (not responding to OPTIONS or SUBSCRIBE)

ABANDONED

This means that the call was canceled by the dialer.

ORIGINATOR_CANCEL

The one who started the call (operator or customer) stopped it before the answer was received (Answer)