Hangup cause

0

UNSPECIFIED

It is issued by the router when none of the other codes fit. This cause usually occurs in situations similar to causes 1, 88, and 100.

1

404

UNALLOCATED_NUMBER

This cause indicates that called side cannot be reached because although the called side number possesses a valid format, currently it is not assigned (assigned).

2

404

NO_ROUTE_TRANSIT_NET

This cause indicates that the equipment sending this cause has received a request for call routing through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network for the following reasons: the transit network does not exist or that particular transit network, although it exists, does not maintain the equipment sending this cause.

3

404

NO_ROUTE_DESTINATION

This cause indicates that called side cannot be reached because a network through which the call has been routed doesn’t maintain a desirable destination. This cause is supported depending on the network.

6

CHANNEL_UNACCEPTABLE

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

7

CALL_AWARDED_DELIVERED

A user has been given an incoming call, and the incoming call connects to the channel already set for that user for similar calls (for example, x.25 virtual calls in a package mode).

16

NORMAL_CLEARING

Normal call termination

17

486

USER_BUSY

The called side cannot take another call because the user's busy state has been detected. This cause value can be created by a called user or network. In case when the user is detected as busy, it is noted that the user’s equipment is compatible with the call.

18

408

NO_USER_RESPONSE

The called side doesn't respond to a message of call establishing, warning, or connection indication during an established period.

19

480

NO_ANSWER

This cause is used when a called side has been warned but is not answering with a connection indication during the prescribed period. A note: this cause is not necessarily generated by the Q.931 procedures but can be caused by the internal network timers.

20

480

SUBSCRIBER_ABSENT

This cause value is used when the mobile station has logged out of the system, the radio connection with the mobile station has not been established, or the personal radio connection user temporary does not possess the address on any user network interface

21

603

CALL_REJECTED

This cause indicates that the equipment sending this cause does not wish to receive this call although it may have accepted this call because the equipment sending this cause is not busy or incompatible. A network also can generate this reason indicating that the call has been rejected due to the restrictions of additional service. The diagnostics field may include additional information about the additional service and the reason for denying.

22

410

NUMBER_CHANGED

This cause is returned to the calling side when the called side’s number specified by the calling side is no longer assigned. The new calling side number may be optionally included in the diagnostics field. When the network does not support this cause, it means the reason №1: unallocated (unassigned) number must be used.

23

410

REDIRECTION_TO_NEW_DESTINATION

This cause is used by the general ISUP protocol mechanism which can be launched by the commutator that decides to establish a call to another called number. This exchange may cause a redirection mechanism that uses this cause value to request a previous exchange participating in the call to route the call to the new number.

25

483

EXCHANGE_ROUTING_ERROR

This cause indicates that the destination point specified by the user cannot be reached because the intermediate commutator has disabled the call due to reaching the limit while executing the hop counter procedure. This cause is generated by the intermediate node that produces a result of 0 when the hop counter value is decreasing.

27

502

DESTINATION_OUT_OF_ORDER

This cause indicates that the destination point specified by the user cannot be reached because the interface of the destination point does not work properly. The ‘does not work properly’ term means that the signaling message could not be delivered to the remote side; for example, physical level failure, level of data transmission channel on the remote side, or the disabled user’s equipment.

28

484

INVALID_NUMBER_FORMAT

This cause indicates that a called side cannot be reached because the called side number has an invalid or incomplete format.

29

501

FACILITY_REJECTED

This cause returns when an additional service requested by the user cannot be provided by the network.

30

RESPONSE_TO_STATUS_ENQUIRY

This cause is included in the STATUS message when the prior receipt of the STATUS INQUIRY was a reason for generating the STATUS message.

31

480

NORMAL_UNSPECIFIED

This reason is used to report a normal event only when none of the other reasons in the normal class apply.

34

503

NORMAL_CIRCUIT_CONGESTION

This cause indicates that currently there is no suitable circuit/channel for call processing.

38

503

NETWORK_OUT_OF_ORDER

This cause indicates that a network is not working properly, and this state is likely to last for a long time so the immediate call retry is unlikely to be successful .

41

503

NORMAL_TEMPORARY_FAILURE

This cause indicates that a network is not working properly, and this state is unlikely to last for a long time; so the user may want to make one more call attempt almost immediately.

42

503

SWITCH_CONGESTION

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

43

ACCESS_INFO_DISCARDED

This cause indicates that a network couldn’t deliver to the remote user information about access according to the request, i.e the information between users, low-level compatibility, high-level compatibility, or subaddress as specified in the diagnostics.

44

503

REQUESTED_CHAN_UNAVAIL

This cause comes back when another side of the interface cannot provide the scheme or channel indicated by the requesting object.

50

FACILITY_NOT_SUBSCRIBED

This cause indicates that a user has requested an additional service that is available but the user is not authorized to use.

52

403

OUTGOING_CALL_BARRED

This cause indicates that although the calling side is a subscriber of the CUG outbound call, the outbound calls are not allowed for this CUG subscriber.

54

403

INCOMING_CALL_BARRED

This cause indicates that although the called side is a CUG subscriber for the inbound call, the inbound calls are not allowed for this CUG subscriber.

57

403

BEARERCAPABILITY_NOTAUTH

This cause indicates that a user has requested a transfer capability that is implemented by the equipment that generated this cause but the user is not authorized to use.

58

503

BEARERCAPABILITY_NOTAVAIL

This cause indicates that a user has requested a transfer capability that is implemented by the equipment that generated this cause but which is currently unavailable.

63

SERVICE_UNAVAILABLE

This cause is used for informing about the cause of service or parameter unavailability only when none of the other reasons in the service class or parameter unavailability apply.

65

488

BEARERCAPABILITY_NOTIMPL

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

66

CHAN_NOT_IMPLEMENTED

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

69

501

FACILITY_NOT_IMPLEMENTED

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

79

501

SERVICE_NOT_IMPLEMENTED

This cause is used for informing about the cause that is related to the unimplemented service or parameter only if none of the other reasons in the class of unimplemented service or parameter apply.

81

INVALID_CALL_REFERENCE

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

88

488

INCOMPATIBLE_DESTINATION

This cause indicates that the equipment sending this cause has received a request to establish a call that has low-level compatibility, high-level compatibility, or other compatibility attributes (for example, data transmission speed) which cannot be implemented.

95

INVALID_MSG_UNSPECIFIED

This reason is used for informing about invalid message cause only if any other reason in the invalid message class does not apply.

96

MANDATORY_IE_MISSING

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

97

MESSAGE_TYPE_NONEXIST

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

98

WRONG_MESSAGE

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

99

IE_NONEXIST

This cause indicates that the equipment sending this cause has received a message including unrecognizable information element (s) because the information element (s) / parameter (s) name (s) is (are) not defined or defined but not implemented by the equipment sending this cause. This reason indicates that the information element (s) has (have) been discarded. However, the information element is not obligated to be present in the message to allow the equipment sending this cause to process the message.

100

INVALID_IE_CONTENTS

This cause indicates that the equipment sending this cause has received the information element that was implemented by it. However, one or several fields in the I.E. are encoded in a way that hasn’t been implemented by the equipment sending this cause

101

WRONG_CALL_STATE

This cause indicates that a message non-compliant with the call state has been received. 

102

504

RECOVERY_ON_TIMER_EXPIRE

This reason indicates that a procedure was initiated by timer expiration connected with error processing procedures. This is often caused by NAT issues. Make sure «NAT Mapping Enable» is activated in your ATA. If it isn’t concerning NAT, sometimes it refers to a provider. Check if another outbound provider can solve a problem.

103

MANDATORY_IE_LENGTH_ERROR

This cause indicates that the equipment sending this cause has received a message including parameters that are not recognized because parameters are not defined or defined but not implemented by the equipment sending this cause. The reason indicates that the parameters have been ignored. Besides, if the equipment sending this cause is an intermediate point thus this cause indicates that the parameter (parameters) was (were) transmitted without changes.

111

PROTOCOL_ERROR

This reason is used for informing about protocol error cause only in case when none of the other causes in the protocol error class apply.

127

INTERWORKING

This reason indicates that an internetwork call (usually an SW56 service call) has ended.

503

MANAGER_REQUEST

This cause is used when you send an API command to end the call.

605

PICKED_OFF

This cause means that the call was picked up from another added number.

606

USER_NOT_REGISTERED

This means you tried to call a SIP user that has not been registered.

609

GATEWAY_DOWN

Gateway is down (does not respond to OPTIONS or SUBSCRIBE)

687

ABANDONED

This means that the call was canceled by the dialer

ORIGINATOR_CANCEL

The call originator (agent or client) ended the call before receiving the answer (Answer)