|
Cause# |
Fixit! |
Cause Summary |
Cause Usage |
| 1 |
N/A |
Unallocated (unassigned number) |
Indicates that the destination requested by the calling user cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated). |
| 2 |
N/A |
No route to specified transit network. |
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 network, while it does exist, does not serve the equipment which is sending the cause. |
| 3 |
N/A |
No route to destination. |
Indicates that the called user cannot be reached because the network through which the call has been routed does not serve the destination desired. |
| 6 |
N/A |
Channel unacceptable. |
Indicates that the channel most recently identified is not acceptable to the sending entity for use in this call. |
| 7 |
N/A |
Call awarded and being delivered in an established channel. |
Indicates that the user is receiving an incoming call, which is being connected to a channel already used by that user for similar calls (e.g., packet-mode X.25 virtual calls). |
| 16 |
N/A |
Normal call clearing. |
Indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. |
| 17 |
N/A |
User busy. |
Used when the called user has indicated the inability to accept another call. It is noted that the user equipment is compatible with the call. |
| 18 |
N/A |
No user responding. |
Used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (defined in Recommendation Q.931 by the expiry of either timer T303 or T310). |
| 19 |
N/A |
No answer from user (user alerted). |
Used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time. This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers. |
| 21 |
N/A |
Call rejected. |
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. |
| 22 |
N/A |
Number changed. |
Returned to a calling user when the called party number indicated by the calling user is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1, unassigned (unallocated) number, shall be used. |
| 26 |
N/A |
Non-selected user clearing. |
Indicates that the specified user has not been awarded the incoming call. |
| 27 |
N/A |
Destination out of order. |
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 signaling message was unable to be delivered to the remote user: eg., a physical layer or data link layer failure at the remote user, user equipment off-line, etc. |
| 28 |
N/A |
Invalid number format (address incomplete). |
Indicates that the called user cannot be reached because the called party number is not a valid format or is not complete. |
| 29 |
N/A |
Facility rejected. |
Returned when a facility requested by the user can not be provided by the network. |
| 30 |
N/A |
Response to STATUS INQUIRY. |
Included in the STATUS message when the reason for generated the STATUS message was the prior receive of a STATUS INQUIRY message. |
| 31 |
N/A |
Normal, unspecified. |
Used to report a normal even only when no other cause in the normal class applies. |
| 34 |
N/A |
No circuit/channel available. |
Indicates that there is no appropriate circuit/channel presently available to handle the call. |
| 38 |
N/A |
Network out of order. |
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 reattempting the call is not likely to be successful. |
| 41 |
N/A |
Temporary failure. |
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. |
| 42 |
N/A |
Switching equipment congestion. |
Indicates that the switching equipmentgenerating this cause is experiencing a period of high traffic. |
| 43 |
N/A |
Access information discarded. |
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 a sub-address as indicated in the diagnostic. |
| 44 |
N/A |
Requested circuit/channel no available. |
Returned when the circuit or channel indicated by the requesting entity can not be provided by the other side of the interface. |
| 47 |
N/A |
Resource unavailable, unspecified. |
Used to report a resource unavailable event only when no other cause in the resource unavailable class applies. |
| 49 |
N/A |
Quality of Service not available. |
Used to report that the requested Quality of Service, as defined in Recommendation X.213, cannot be provided (e.g., throughput ro transit delay cannot be supported). |
| 50 |
N/A |
Requested facility not subscribed. |
Indicates that the requested supplementary service could not be provided by the network because the user has not completed the necessary administrative arrangements with its supporting networks. |
| 57 |
N/A |
Bearer capability not authorized. |
Indicates that the user has requested a bearer capability implemented by the equipment that generated this cause that the user is not authorized to use. |
| 58 |
N/A |
Bearer capability not presently abvailable. |
Indicates that the user has requested a bearer capability implemented by the equipment that generated this cause which is not available at this time. |
| 63 |
N/A |
Service or option ot available, unspecified. |
Used to report a service or option not available event only when no other cause in the service or option not available class applies. |
| 65 |
N/A |
Bearer capability not implemented. |
Indicates that the equipment sending this cause does not support the bearer capability requested. |
| 66 |
N/A |
Channel type not implemented. |
Indicates that the equipment sending this cause does not support the channel type requested. |
| 69 |
N/A |
Requested facility not implemented. |
Indicates that the equipment sending this cause does not support the requested supplementary service. |
| 70 |
N/A |
Only restricted digital information bearer capability is availbale. |
Indicates that a device has requested an unrestricted bearer service but the equipment sending this cause only supports the restricted version of the requested bearer capability. |
| 79 |
N/A |
Service or option not implemented, unspecified. |
Used to report a service or option not implemented event only only when no other cause in the service or option not implemented class applies. |
| 81 |
N/A |
Invalid call reference value. |
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. |
| 82 |
N/A |
Identified channel does not exist. |
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 channelson 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. |
| 83 |
N/A |
A suspended call exists, but this call identify does not. |
Indicates that a call resume has been attempted with a call identity that differs from that in use for any presently suspended call(s). |
| 84 |
N/A |
Call identity in use. |
Indicates that the network has received a call suspended request. The call suspend request contained 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. |
| 85 |
N/A |
No call suspended. |
Indicates that the network has received a call resume request. The call resume request contained a Call identity information element which presently does not indicate any suspended call within the domain interfaces over which calls may be resumed. |
| 86 |
N/A |
Call having the requested call identity has been cleared. |
Indicates that the network has received call resume request. The call resume request contained a Call identity information element which once indicated a suspended call; however, that suspended call was cleared while suspended (either by network timeout or by remote user). |
| 88 |
N/A |
Incompatible destination. |
Indicates that the equipment sending this cause has received a request to establish a call has a low layer compatibility, high layer compatibility, or other compatibility attributes (e.g., data rate) which cannot be accommodated. |
| 91 |
N/A |
Invalid transit network selection. |
Indicates that a transit network identification was received which is of an incorrect format as defined in Annex C/Q.931. |
| 95 |
N/A |
Invalid message, unspecified. |
Used to report an invlaid message event only when no other cause in the invlaid message class applies. |
| 96 |
N/A |
Mandatory information element is missing. |
Indicates that the equipment sending this cause has received a message that is missing an information element that must be present in the message before that message can be processed. |
| 97 |
N/A |
Message type non-existent or not implemented. |
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. |
| 98 |
N/A |
Message not compatible with call state or message type non-existent or not implememted. |
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. |
| 99 |
N/A |
Information element non-existent or not imlememted. |
Indicates that the equipment sending this cause has received a message that includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. 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. |
| 100 |
N/A |
Invalid information element contents. |
Indicates that the equipment sending this cause has received an information element which it has implemented; however, one or more of the fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause. |
| 101 |
N/A |
Message not compatible with call state. |
Indicates that a message has been received which is incompatible with the call state. |
| 102 |
N/A |
Recovery on timer expiry. |
Indicates that a procedure has been initiated by the expiry of a timer in association with Q.931 error handling procedures. |
| 111 |
N/A |
Protocol error, unspecified. |
Used to report a protocol error event only when no other cause in the protocol error class applies. |
| 127 |
N/A |
Interworking, unspecified. |
Indicates there has been interworking with a network that does not provide causes for actions it takes; thus, the precise cause for a message being sent cannot be ascertained. |
ModemHelp.Net Recommends: 
