好消息，超酷的在线虚拟网络实验室上线了！点击开始实验

Hex

Cause

Explanation

81

Cause No. 1 - Unallocated (unassigned) number

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

82

Cause No. 2 - No route to specified transit network (national use)

This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which 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 that particular transit network, while it does exist, does not serve the equipment which is sending this cause.

This cause is supported on a network-dependent basis.

83

Cause No. 3 - No route to destination

This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network-dependent basis.

84

Cause No. 4 - Send special information tone

This cause indicates that the called party cannot be reached for reasons that are of a long term nature and that the special information tone should be returned to the calling party.

85

Cause No. 5 - Misdialled trunk prefix (national use)

This cause indicates the erroneous inclusion of a trunk prefix in the called party number.

86

Cause No. 6 - Channel unacceptable

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

87

Cause No. 7 - Call awarded and being delivered in an established channel

This cause indicates that the user has been awarded the incoming call, and that the incoming call is being connected to a channel already established to that user for similar calls (e.g. packet-mode X.25 virtual calls).

88

Cause No. 8 - Preemption

This cause indicates that the call is being preempted.

89

Cause No. 9 - Preemption - circuit reserved for reuse

This cause indicates that the call is being preempted and the circuit is reserved for reuse by the preempting exchange.

90

Cause No. 16 - Normal call clearing

This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared.

Under normal situations, the source of this cause is not the network.

91

Cause No. 17 - User busy

This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determine user busy, it is noted that the user equipment is compatible with the call.

92

Cause No. 18 - No user responding

This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated.

93

Cause No. 19 - No answer from user (user alerted)

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

94

Cause No. 20 - Subscriber absent

This cause value is used when a mobile station has logged off, radio contact is not obtained with a mobile station or if a personal telecommunication user is temporarily not addressable at any user-network interface.

95

Cause No. 21 - Call rejected 

This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible.

This cause may also be generated by the network, indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection.

96

Cause No. 22 - Number changed

This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this cause value, cause No. 1, unallocated (unassigned) number shall be used.

9A

Cause No. 26 - Non-selected user clearing

This cause indicates that the user has not been awarded the incoming call.

9B

Cause No. 27 - Destination out of order

This cause indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was unable to be delivered to the remote party; e.g. a physical layer or data link layer failure at the remote party, or user equipment off-line.

9C

Cause No. 28 - Invalid number format (address incomplete)

This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. 

Note: This condition may be determined:

• immediately after reception of an ST signal; or
• on time-out after the last received digit.

9D

Cause No. 29 - Facility rejected

This cause is returned when a supplementary service requested by the user cannot be provided by the network.

9E

Cause No. 30 - Response to STATUS ENQUIRY

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

9F

Cause No. 31 - Normal, unspecified

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

A2

Cause No. 34 - No circuit/channel available

This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

A6

Cause No. 38 - Network out of order

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g. immediately re-attempting the call is not likely to be successful.

A7

Cause No. 39 - Permanent frame mode connection out-of-service

This cause is included in a STATUS message to indicate that a permanently established frame mode connection is out-of-service (e.g. due to equipment or section failure) (see Annex A/Q.933).

A8

Cause No. 40 - Permanent frame mode connection operational

This cause is included in a STATUS message to indicate that a permanently established frame mode connection is operational and capable of carrying user information (see Annex A/Q.933).

A9

Cause No. 41 - Temporary failure

This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g. the user may wish to try another call attempt almost immediately.

AA

Cause No. 42 - Switching equipment congestion

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

AB

Cause No. 43 - Access information discarded

This cause indicates that the network could not deliver access information to the remote user as requested, i.e. user-to-user information, low layer compatibility, high layer compatibility, or sub-address, as indicated in the diagnostic.

It is noted that the particular type of access information discarded is optionally included in the diagnostic.

AC

Cause No. 44 - Requested circuit/channel not available

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

AE

Cause No. 46 - Precedence call blocked

This cause indicates that there are no preemptable circuits or that the called user is busy with a call of equal or higher preemptable level.

AF

Cause No. 47 - Resource unavailable, unspecified

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

B1

Cause No. 49 - Quality of Service not available

This cause is used to report that the requested Quality of Service, as defined in Recommendation X.213, cannot be provided (e.g. throughput or transit delay cannot be supported).

B2

Cause No. 50 - Requested facility not subscribed

This cause indicates that the user has requested a supplementary service which is implemented by the equipment which generated this cause, but the user is not authorized to use.

B5

Cause No. 53 - Outgoing calls barred within CUG

This cause indicates that although the calling party is a member of the CUG for the outgoing CUG call, outgoing calls are not allowed for this member of the CUG.

B7

Cause No. 55 - Incoming calls barred within CUG

This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed to this member of the CUG.

B9

Cause No. 57 - Bearer capability not authorized

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

BA

Cause No. 58 - Bearer capability not presently available

This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.

BE

Cause No. 62 - Inconsistency in designated outgoing access information and subscriber class

This cause indicates that there is an inconsistency in the designated outgoing access information and subscriber class.

BF

Cause No. 63 - Service or option not available, unspecified

This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies. 

C1

Cause No. 65 - Bearer capability not implemented 

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

C2

Cause No. 66 - Channel type not implemented

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

C5

Cause No. 69 - Requested facility not implemented

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

C6

Cause No. 70 - Only restricted digital information bearer capability is available (national use) 

This cause indicates that the calling party has requested an unrestricted bearer service but that the equipment sending this cause only supports the restricted version of the requested bearer capability.

CF

Cause No. 79 - Service or option not implemented, unspecified

This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.

D1

Cause No. 81 - Invalid call reference value

This cause indicates that the equipment sending this cause has received a message with a call reference which is not currently in use on the user-network interface.

D2

Cause No. 82 - Identified channel does not exist

This cause indicates that the equipment sending this cause has received a request to use a channel not activated on the interface for a call.

For example, if a user has subscribed to those channels on a primary rate interface numbered from 1 to 12 and the user equipment or the network attempts to use channels 13 through 23, this cause is generated.

D3

Cause No. 83 - A suspended call exists, but this call identity does not

This cause indicates that a call resume has been attempted with a call identity which differs from that in use for any presently suspended call(s).

D4

Cause No. 84 - Call identity in use

This cause indicates that the network has received a call suspended request containing a call identity (including the null call identity) which is already in use for a suspended call within the domain of interfaces over which the call might be resumed.

D5

Cause No. 85 - No call suspended

This cause indicates that the network has received a call resume request containing a call identity information element which presently does not indicate any suspended call within the domain of interfaces over which calls may be resumed.

D6

Cause No. 86 - Call having the requested call identity has been cleared

This cause indicates that the network has received a call resume request containing a call identity information element indicating a suspended call that has in the meantime been cleared while suspended (either by network timeout or by the remote user).

D7

Cause No. 87 - User not member of CUG

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG or that the calling user is an ordinary subscriber calling a CUG subscriber.

D8

Cause No. 88 - Incompatible destination

This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility, high layer compatibility, or other compatibility attributes (e.g. data rate) which cannot be accommodated.

DA

Cause No. 90 - Non-existent CUG

This cause indicates that the specified CUG does not exist.

DB

Cause No. 91 - Invalid transit network selection (national use)

This cause indicates that a transit network identification was received which is of an incorrect format as defined in Annex C/Q.931.

DF

Cause No. 95 - Invalid message, unspecified

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

E0

Cause No. 96 - Mandatory information element is missing

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

E1

Cause No. 97 - Message type non-existent or not implemented

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

E2

Cause No. 98 - Message not compatible with call state or message type non-existent or not implemented

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

E3

Cause No. 99 - Information element/parameter non-existent or not implemented 

This cause indicates that the equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element identifier(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. 

This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

E4

Cause No. 100 - Invalid information element contents

This cause indicates that the equipment sending this cause has received an information element which it has implemented; however, one or more fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause.

E5

Cause No. 101 - Message not compatible with call state

This cause indicates that a message has been received which is incompatible with the call state.

E6

Cause No: 102 - Recovery on timer expiry

This cause indicates that a procedure has been initiated by the expiry of a timer in association with error handling procedures.

E7

Cause No. 103 - Parameter non-existent or not implemented - passed on (national use)

This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending the cause.

The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed on unchanged.

EE

Cause No: 110 - Message with unrecognized parameter discarded

This cause indicates that the equipment sending this cause has discarded a received message which includes a parameter that is not recognized.

EF

Cause No. 111 - Protocol error, unspecified

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

FF

Cause No. 127 - interworking, unspecified

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes. Thus, the precise cause for a message which is being sent cannot be ascertained.