Cause codes and defnitions:

Cause No. 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 ormat, it is not currently assigned (allocated).
Cause No. !: no route to s"ecifed transit net#or$. This cause indicates that the
equi"ment sending this cause has received a request to route the call through a
"articular transit net#or$ #hich it does not recogni%e. The equi"ment sending this
cause does not recogni%e the transit net#or$ either because the transit net#or$ does
not e&ist or because that "articular net#or$, #hile it does e&ist, does not serve the
equi"ment that is sending this cause.
This cause is su""orted on a net#or$'de"endent basis.
Cause No. (: no route to destination. This cause indicates that the called user cannot
be reached because the net#or$ through #hich the call has been routed does not
serve the destination desired.
This cause is su""orted on a net#or$'de"endent basis.
Cause No. ): channel unacce"table. This cause indicates that the channel used in this
call is not acce"table to the sending entity.
Cause No.*: call a#arded and being delivered in an established channel. This cause
indicates that the user is receiving an incoming call, #hich is being connected to a
channel already used by that user or similar calls (e.g., "ac$et'mode +.!, virtual
calls).
Cause No. 1): normal call clearing. This cause indicates that the call is being cleared
because one o the users involved in the call has requested that the call be cleared.
Under normal situations, the source o this cause is not the net#or$.
Cause No. 1*: user busy. This cause is used #hen the called user has indicated the
inability to acce"t another call.
-t is noted that the user equi"ment is com"atible #ith call.
Cause No. 1.: no user res"onding. This cause is used #hen a user does not res"ond
to a call establishment message #ith either an alerting or connect indication #ithin
the "rescribed "eriod o time allocated (defned in /ecommendation 0.1(1 by the
e&"iry o either timer T(2( or T(12).
Cause No. 11: no ans#er rom user (user alerted). This cause is used #hen a user has
"rovided an alerting indication but has not "rovided a connect indication #ithin a
"rescribed "eriod o time.
This cause is not necessarily generated by 0.1(1 "rocedures but may be generated
by internal net#or$ timers.
Cause No. !1: call re3ected. This cause indicates that the equi"ment sending this
cause does not #ish to acce"t this call, although it could have acce"ted the call
because the equi"ment sending this cause is neither busy nor incom"atible.
Cause No. !!: number changed. This cause is returned to a calling user #hen the
called "arty number indicated by the calling user is no longer assigned. The ne#
called "arty number may o"tionally be included in the diagnostic feld. - a net#or$
does not su""ort this ca"ability, cause No. 1, unassigned (unallocated) number, shall
be used.
Cause No. !): non'selected user clearing. This cause indicates that the s"ecifed user
has not been a#arded the incoming call.
Cause No. !*: destination out o order. This cause indicates that the destination
indicated by the user cannot be reached because the interace to the destination is
not unctioning correctly. The term 4not unctioning correctly4 indicates that a
signaling message #as unable to be delivered to the remote user: e.g., a "hysical
layer or data lin$ layer ailure at the remote user, user equi"ment o5'line, etc.
Cause No. !.: invalid number ormat (address incom"lete). This cause indicates that
the called user cannot be reached because the called "arty number is not a valid
ormat or is not com"lete.
Cause No. !1: acility re3ected. This cause is returned #hen a acility requested by the
user cannot be "rovided by the net#or$.
Cause No. (2: res"onse to 6T7TU6 -N0U-/8. This cause is included in the 6T7TU6
message #hen the reason or generated the 6T7TU6 message #as the "rior receive
o a 6T7TU6 -N0U-/8 message.
Cause No. (1: normal, uns"ecifed. This cause is used to re"ort a normal even only
#hen no other cause in the normal class a""lies.
Cause No. (9: no circuit:channel available. This cause indicates that there is no
a""ro"riate circuit:channel "resently available to handle the call.
Cause No. (.: net#or$ out o order. This cause indicates that the net#or$ is not
unctioning correctly and that: the condition is li$ely to last a relatively long "eriod o
time: e.g., immediately reattem"ting the call is not li$ely to be successul.
Cause No. 91: tem"orary ailure. This cause indicates that the net#or$ is not
unctioning correctly and that the condition is not li$ely to last a long "eriod o time:
e.g., the user may #ish to try another call attem"t almost immediately.
Cause No. 9!: s#itching equi"ment congestion. This cause indicates that the
s#itching equi"ment generating this cause is e&"eriencing a "eriod o high tra;c.
Cause No. 9(: access inormation discarded. This cause indicates that the net#or$
could not deliver access inormation to the remote user as requested: i.e., user'to'
user inormation, lo# layer com"atibility, high layer com"atibility, or a sub'address as
indicated in the diagnostic.
-t is noted that the "articular ty"e o access inormation discarded is o"tionally
included in the diagnostic.
Cause No. 99: requested circuit:channel not available. This cause is returned #hen
the circuit or channel indicated by the requesting entity cannot be "rovided by the
other side o the interace.
Cause No. 9*: resource unavailable, uns"ecifed. This cause is used to re"ort a
resource unavailable event only #hen no other cause in the resource unavailable
class a""lies.
Cause No 91: 0uality o 6ervice not available. This cause is used to re"ort that the
requested 0uality o 6ervice, as defned in /ecommendation +.!1(, cannot be
"rovided (e.g., through"ut or transit delay cannot be su""orted).
Cause No. ,2: requested acility not subscribed. This cause indicates that the
requested su""lementary service could not be "rovided by the net#or$ because the
user has not com"leted the necessary administrative arrangements #ith its
su""orting net#or$s.
Cause No ,*: bearer ca"ability not authori%ed. This cause indicates that the user has
requested a bearer ca"ability im"lemented by the equi"ment that generated this
cause that the user is not authori%ed to use.
Cause No. ,.: bearer ca"ability not "resently available. This cause indicates that the
user has requested a bearer ca"ability im"lemented by the equi"ment that
generated this cause #hich is not available at this time.
Cause No )(: service or o"tion not available, uns"ecifed. This cause is used to re"ort
a service or o"tion not available event only #hen no other cause in the service or
o"tion not available class a""lies.
Cause No. ),: bearer ca"ability not im"lemented. This cause indicates that the
equi"ment sending this cause does not su""ort the bearer ca"ability requested.
Cause No. )): channel ty"e not im"lemented. This cause indicates that the
equi"ment sending this cause does not su""ort the channel ty"e requested.
Cause No. )1: requested acility not im"lemented. This cause indicates that the
equi"ment sending this cause does not su""ort the requested su""lementary
service.
Cause No. *2: only restricted digital inormation bearer ca"ability is available. This
cause indicates that a device has requested an unrestricted bearer service but the
equi"ment sending this cause only su""orts the restricted version o the requested
bearer ca"ability.
Cause No. *1: service or o"tion not im"lemented, uns"ecifed. This cause is used to
re"ort a service or o"tion not im"lemented event only #hen no other cause in the
service or o"tion not im"lemented class a""lies.
Cause No. .1: invalid call reerence value. This cause indicates that the equi"ment
sending this cause has received a message #ith a call reerence #hich is not
currently in use on the user'net#or$ interace.
Cause No. .!: identifed channel does not e&ist. This cause indicates that the
equi"ment sending this cause has received a request to use a channel not activated
on the interace or a call. <or e&am"le, i a user has subscribed to those channels on
a "rimary rate interace numbered rom 1 to 1! and the user equi"ment or the
net#or$ attem"ts to use channels 1( through !(, this cause is generated.
Cause No. .(: a sus"ended call e&ists, but this call identiy does not. This cause
indicates that a call resume has been attem"ted #ith a call identity #hich di5ers
rom that in use or any "resently sus"ended call(s).
Cause No. .9: call identity in use. This cause indicates that the net#or$ has received
a call sus"end request. The call sus"end request contained a call identity (including
the null call identity) #hich is already in use or a sus"ended call #ithin the domain o
interaces over #hich the call might be resumed.
Cause No. .,: no call sus"ended. This call indicates that the net#or$ has received a
call resume request. The call resume request contained a call identity inormation
element that "resently does not indicate any sus"ended call #ithin the domain
interaces over #hich calls may be resumed.
Cause No. .): call having the requested call identity has been cleared. This cause
indicates that the net#or$ has received a call resume request. The call resume
request contained a call identity inormation element that once indicated a
sus"ended call= ho#ever, that sus"ended call #as cleared #hile sus"ended (either by
net#or$ timeout or by remote user).
Cause No. ..: incom"atible destination. This cause indicates that the equi"ment
sending this cause has received a request to establish a call that has a lo# layer
com"atibility, high layer com"atibility, or other com"atibility attributes (e.g., data
rate) that cannot be accommodated.
Cause No. 11: invalid transit net#or$ selection. This cause indicates that a transit
net#or$ identifcation o an incorrect ormat as defned in 7nne& C:0.1(1 #as
received.
Cause No. 1,: invalid message, uns"ecifed. This cause is used to re"ort an invalid
message event only #hen no other cause in the invalid message class a""lies.
Cause No. 1): mandatory inormation element is missing. This cause indicates that
the equi"ment sending this cause has received a message that is missing an
inormation element that must be "resent in the message beore that message can
be "rocessed.
Cause No. 1*: message ty"e non'e&istent or not im"lemented. This cause indicates
that the equi"ment sending this cause has received a message #ith a message ty"e
it does not recogni%e either because this is a message not defned or defned but not
im"lemented by the equi"ment sending this cause.
Cause No. 1.: message not com"atible #ith call state or message ty"e non'e&istent
or not im"lemented. This cause indicates that the equi"ment sending this cause has
received a message such that the "rocedures do not indicate that this is a
"ermissible message to receive #hile in the call state, or a 6T7TU6 message #as
received indicating an incom"atible call state.
Cause No. 11: inormation element non'e&istent or not im"lemented. This cause
indicates that the equi"ment sending this cause has received a message that
includes inormation elements not recogni%ed because the inormation element
identifer is not defned or it is defned but not im"lemented by the equi"ment
sending the cause. >o#ever, the inormation element is not required to be "resent in
the message in order or the equi"ment sending the cause to "rocess the message.
Cause No. 122: invalid inormation element contents. This cause indicates that the
equi"ment sending this cause has received an inormation element #hich it has
im"lemented= ho#ever, one or more o the felds in the inormation element are
coded in a #ay that has not been im"lemented by the equi"ment sending this
Cause No 121: message not com"atible #ith call state. This cause indicates that a
message has been received that is incom"atible #ith the call state.
Cause No. 12!: recovery on timer e&"iry. This cause indicates that a "rocedure has
been initiated by the e&"iry o a timer in association #ith 0.1(1 error handling
"rocedures.
Cause No. 111: "rotocol error, uns"ecifed. This cause is used to re"ort a "rotocol
error event only #hen no other cause in the "rotocol error class a""lies.
Cause No. 1!*: inter#or$ing, uns"ecifed. This cause indicates there has been
inter#or$ing #ith a net#or$ that does not "rovide causes or actions it ta$es= thus,
the "recise cause or a message being sent cannot be ascertained.