This provides definitions to the Clear causes in Q931 messages.<\/p>\n
Normal class
\nCause #1 “unallocated (unassigned) number”
\nThis cause indicates that the destination requested by the calling user cannot be reached
\nbecause, although the number is in a valid format, it is not currently assigned (allocated).<\/p>\n
Cause #2 “no route to specified transit network”
\nThis cause indicates that the equipment sending this cause has received a request to route
\nthe call through a particular transit network which it does not recognise. The equipment
\nsending this cause does not recognise the transit network either because the transit network\u00a0does not exist or because that particular transit network, while it does exist, does not service\u00a0the equipment which is sending this cause.<\/p>\n
This cause is supported on a network-dependent basis.<\/p>\n
Cause #3 “no route to destination”
\nThis cause indicates that the called user cannot be reached because the network through
\nwhich the call has been routed does not serve the destination desired.
\nThis cause is supported on a network-dependent basis.<\/p>\n
Cause #6 “channel unacceptable”
\nThis cause indicates the channel most recently identified is not acceptable to the sending
\nentity for use in this call.<\/p>\n
Cause #7 “call awarded and being delivered in an established\u00a0channeP’
\nThis cause indicates that the user has been awarded the incoming call, and that the\u00a0incoming call is being connected to a channel already established to that user for similar\u00a0calls (e.g. packet-mode X.25 virtual calls).<\/p>\n
Cause #16 “normal call clearing”
\nThis cause indicates that the call is being cleared because one of the users involved in the
\ncall has requested that the call be cleared.
\nUnder normal situations, the source of this cause is not the network.<\/p>\n
Cause #17 “user busy”
\nThis cause is used when the called user has indicated the inability to accept another call.
\nIt is noted that the user equipment is compatible with the call.<\/p>\n
Cause #18 “no user responding”
\nThis cause is used when a user does not respond to a call establishment message with
\neither an alerting or connect indication within the prescribed period of time allocated
\n(defined in ETS 300 102-1 by the expiry of either timer T3 03 or T3 10).<\/p>\n
Cause #19 “no answer from user (user alerted)”
\nThis cause is used when a user has provided an alerting indication but has not provided a
\nconnect indication within a prescribed period of time.
\nNOTE:This cause is not necessarily generated by ETS 300 102-1 procedures but may be
\ngenerated by internal network timers.<\/p>\n
Cause #21 “call rejected”
\nThis cause indicates that the equipment sending this cause does not wish to accept this
\ncall, although it could have accepted the call because the equipment sending this cause is
\nneither busy nor incompatible.<\/p>\n
Cause #22 “number changed”
\nThis cause is returned to a calling user when the called party number indicated by the
\ncalling user is no longer assigned. The new called party number may optionally be included\u00a0in the diagnostic field. If a network does not support this capability, cause #1 “unallocated\u00a0(unassigned) number” shall be used.<\/p>\n
Cause #27 “destination out of order”
\nThis cause indicates that the destination indicated by the user cannot be reached because
\nthe interface to the destination is not functioning correctly. The term “not functioning
\ncorrectly” indicates that a signalling message was unable to be delivered to the remote user;\u00a0e.g. a physical layer or data link layer failure at the remote user, user equipment off-line, etc.
\nCause #29 “facility rejected”
\nThis cause is returned when a facility requested by the user cannot be provided by
\nthe network.<\/p>\n
Cause #30 “response to status enquiry”
\nThis cause is included in the STATUS message when the reason for generating the
\nSTATUS message was the prior receipt of a STATUS ENQUIRY message.<\/p>\n
Cause #31 “normal, unspecified”
\nThis cause is used to report a normal event only when no other cause in the normal class
\napplies.
\nResource unavailable class<\/p>\n
Cause #34 “no circuit\/channel available”
\nThis cause indicates that there is no appropriate circuit\/channel presently available to handle
\nthe call.<\/p>\n
Cause #38 “network out of order”
\nThis cause indicates that the network is not functioning correctly and that the condition is
\nlikely to last a relatively long period of time; e.g. immediately re-attempting the call is not
\nlikely to be successful.<\/p>\n
Cause #41 “temporary failure”
\nThis cause indicates that the network is not functioning correctly and that the condition is not\u00a0likely to last a long period of time; e.g. the user may wish to try another call attempt almost\u00a0immediately.<\/p>\n
Cause #42 “switching equipment congestion”
\nThis cause indicates that the switching equipment generating this cause is experiencing a
\nperiod of high traffic.<\/p>\n
Cause #43 “access information discarded”
\nThis cause indicates that the network could not deliver access information to the remote
\nuser as requested; i.e. a user-to-user information, low layer compatibility, high layer
\ncompatibility, or subaddress as indicated in the diagnostic.
\nIt is noted that the particular type of access information discarded is optionally included in
\nthe diagnostic.<\/p>\n
Cause #44 “requested circuit\/channel not available”
\nThis cause is returned when the circuit or channel indicated by the requesting entity cannot
\nbe provided by the other side of the interface.<\/p>\n
Cause #47 “resource unavailable, unspecified”
\nThis cause is used to report a resource unavailable event only when no other cause in the
\nresource unavailable class applies.
\nService or option not available class<\/p>\n
Cause #49 “quality of service not available”
\nThis cause is used to report that the requested quality of service, as defined in CCITT
\nRecommendation X.213, cannot be provided, (e.g. throughput or transit delay cannot be
\nsupported).<\/p>\n
Cause #50 “requested facility not subscribed”
\nThis cause indicates that the requested supplementary service could not be provided by the\u00a0network because the user has not completed the necessary administrative arrangements\u00a0with its supporting network.<\/p>\n
Cause #57 “bearer capability not authorised”
\nThis cause indicates that the user has requested a bearer capability which is implemented
\nby the equipment which generated this cause but the user is not authorised to use.<\/p>\n
Cause #58 “bearer capability not presently available”
\nThis cause indicates that he user has requested a bearer capability which is implemented by\u00a0the equipment which generated this cause but which is not available at this time.<\/p>\n
Cause #63 “service or option not available “unspeciried”
\nThis cause is used to report a service or option not available event only when no other
\ncause in the service or option not available class applies. Service or option not implemented class<\/p>\n
Cause #65 “bearer capability not implemented”
\nThis cause indicates that the equipment sending this cause does not support the bearer
\ncapability requested.<\/p>\n
Cause #66 “channel type not implemented”
\nThis cause indicates that the equipment sending this cause does not support the channel
\ntype requested.<\/p>\n
Cause #69 “requested facility not implemented”
\nThis cause indicates that the equipment sending this cause does not support the requested
\nsupplementary service.<\/p>\n
Cause #70 “only restricted digital information bearer capability is available”
\nThis cause indicates that one equipment has requested an unrestricted bearer service but
\nthat the equipment sending this cause only supports the restricted version of the requested
\nbearer capability.<\/p>\n
Cause #79 “service or option not implemented, unspecified”<\/p>\n
This cause is used to report a service or option not implemented event only when no other
\ncause in the service or option not implemented class applies.
\nInvalid message (e.g. parameter out of range) class<\/p>\n
Cause #81 “invalid call reference value”
\nThis cause indicates that the equipment sending this cause has received a message with a
\ncall reference which is not currently in use on the usernetwork interface.<\/p>\n
Cause #82 9dentified channel does not exist”
\nThis cause indicates that the equipment sending this cause has received a request to use a
\nchannel not activated on the interface for a call. For example, if a user has subscribed to
\nthose channels on a primary rate interface numbered from 1 to 12 and the user equipment
\nor the network attempts to use channels 13 through 23, this cause is generated.<\/p>\n
Cause #83 “a suspended call exists, but this call identity does noV
\nThis cause indicates that a call resume has been attempted with a call identity which differs\u00a0from that in use for any presently suspended call(s).<\/p>\n
Cause #84 “call identity in use”
\nThis cause indicates that the network has received a call suspend request. The call suspend
\nrequest contained a call identity (including the null call identity) which is already in use for a\u00a0suspended call within the domain of interfaces over which the call might be resumed.<\/p>\n
Cause #85 “no call suspended”
\nThis cause indicates that the network has received a call resume request. The call resume
\nrequest contained a Call identity information element which presently does not indicate any
\nsuspended call within the domain of interfaces over which calls may be resumed.<\/p>\n
Cause #86 “call having the requested call identity has been cleared”
\nThis cause indicates that the network has received a call resume request. The call resume
\nrequest contained a Call identity information element which once indicated a suspended
\ncall; however, that suspended call was cleared while suspended (either by network timeout
\nor by the remote user).<\/p>\n
Cause #88 “incompatible destination”
\nThis cause indicates that the equipment sending this cause has received a request to
\nestablish a call which has low layer compatibility, high layer compatibility, or other
\ncompatibility attributes (e.g. data rate) which cannot be accommodated.<\/p>\n
Cause #90 “destination address missing or incomplete” This cause indicates that he
\ncalled user cannot be reached because the called party number is not in a valid format or is
\nnot complete.<\/p>\n
Cause #91 “invalid transit network selection”
\nThis cause indicates that a transit network identification was received which is of an
\nincorrect format as defined in Annex C.<\/p>\n
Cause #95 “invalid message, unspecified”
\nThis cause is used to report an invalid message event only when no other cause in the
\ninvalid message class applies.
\nProtocol error (e.g. unknown message) class<\/p>\n
Cause #96 “mandatory information element is missing”
\nThis cause indicates that the equipment sending this cause has received a message which
\nis missing an information element which must be present in the message before that
\nmessage can be processed.<\/p>\n
Cause “97 “message type non-existent or not implemented”
\nThis cause indicates that the equipment sending this cause has received a message with a
\nmessage type it does not recognise either because this is a message not defined or defined
\nbut not implemented by the equipment sending this cause.<\/p>\n
Cause #98 “message not compatible with call state or messages type
\nnon-existent or not implemented”
\nThis cause indicates that the equipment sending this cause has received a message such
\nthat the procedures do not indicate that this is a permissible message to receive while in the\u00a0call state, or a STATUS message was received indicating an incompatible call state.<\/p>\n
Cause #99 “information element non-existent or not implemented”
\nThis cause indicates that the equipment sending this cause has received a message which
\nincludes information elements not recognised because the information element identifier is\u00a0not defined or it is defined but not implemented by the equipment sending the cause.
\nHowever, the information element is not required to be present in the message in order for
\nthe equipment sending the cause to process the message.<\/p>\n
Cause #100 “invalid information element contents”
\nThis cause indicates that the equipment sending this cause has received an information
\nelement which it has implemented; however, one or more of the fields in the information
\nelement are coded in such a way which has not been implemented by the equipment
\nsending this cause.<\/p>\n
Cause #101 “message not compatible with call state”
\nThis cause indicates that a message has been received which is incompatible with the call
\nstate.<\/p>\n
Cause #111 “protocol error, unspecified”
\nThis cause is used to report a protocol error event only when no other cause in the protocol
\nerror class applies.Interworking class<\/p>\n
Cause #127 interworking, unspecified”
\nThis cause indicates that there has been interworking with a network which does not provide\u00a0causes for actions it takes; thus, the precise cause for a message which is being sent cannot\u00a0be ascertained.<\/p>\n","protected":false},"excerpt":{"rendered":"
This provides definitions to the Clear causes in Q931 messages. Normal class Cause #1 “unallocated (unassigned) number” This cause 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). Cause #2 “no route to specified transit network” This […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[11,7],"tags":[84],"class_list":["post-1290","post","type-post","status-publish","format-standard","hentry","category-knowledge","category-technical","tag-isdn-pri"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p5daZy-kO","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1290"}],"version-history":[{"count":2,"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1290\/revisions"}],"predecessor-version":[{"id":1541,"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1290\/revisions\/1541"}],"wp:attachment":[{"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cyber-cottage.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}