Cause No.

1 "unassigned (unallocated) number" (UMTS specific cause values for ca ll control) This cause indicates that the destination requested by the mobile station cannot be reached because, although the number is in a valid format, it is not current ly assigned (allocated). Cause value = 2 IMSI unknown in HLR (Causes related to MS identification) This cause is sent to the MS if the MS is not known (registered) in the HLR. Thi s cause code does not affect operation of the GPRS service, although is may be u sed by a GMM procedure. Cause value = 3 Illegal MS (Causes related to MS identification) This cause is s ent to the MS when the network refuses service to the MS either because an ident ity of the MS is not acceptable to the network or because the MS does not pass t he authentication check, i.e. the SRES received from the MS is different from th at generated by the network. When used by an MM procedure, except the authentica tion procedure, this cause does not affect operation of the GPRS service. Cause No. 3 "no route to destination" (UMTS specific cause values for call contr ol) This cause indicates that the called user cannot be reached because the netw ork through which the call has been routed does not serve the destination desire d. Cause value = 4 IMSI unknown in VLR (Causes related to MS identification) This c ause is sent to the MS when the given IMSI is not known at the VLR. Cause value = 5 IMEI not accepted (Causes related to MS identification) This cau se is sent to the MS if the network does not accept emergency call establishment using an IMEI. Cause value = 6 Illegal ME (Causes related to MS identification) This cause is s ent to the MS if the ME used is not acceptable to the network, e.g. blacklisted. When used by an MM procedure, this cause does not affect operation of the GPRS service. Cause No. 6 "channel unacceptable" (UMTS specific cause values for call control) This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call. Cause value = 7 GPRS services not allowed (Additional cause codes for GMM) This cause is sent to the MS if it requests an IMSI attach for GPRS services, but is not allowed to operate GPRS services. Cause value = 8 GPRS services and non-GPRS services not allowed (Additional caus e codes for GMM) This cause is sent to the MS if it requests a combined IMSI att ach for GPRS and non-GPRS services, but is not allowed to operate either of them . Cause No. 8 "operator determined barring" (GPRS specific cause values for sessio n management) This cause indicates that the MS has tried to access a service tha t the MS's network operator or service provider is not prepared to allow. Cause value = 9 MS identity cannot be derived by the network (Additional cause c odes for GMM) This cause is sent to the MS when the network cannot derive the MS 's identity from the P-TMSI in case of inter-SGSN routing area update. Cause value = 10 Implicitly detached (Additional cause codes for GMM) This cause is sent to the MS either if the network has implicitly detached the MS, e.g. so me while after the Mobile reachable timer has expired, or if the GMM context dat a related to the subscription dose not exist in the SGSN e.g. because of a SGSN restart. Cause value = 11 PLMN not allowed (Cause related to subscription options) This c ause is sent to the MS if it requests location updating in a PLMN where the MS, by subscription or due to operator determined barring is not allowed to operate. Cause value = 12 Location Area not allowed (Cause related to subscription option s) This cause is sent to the MS if it requests location updating in a location a rea where the MS, by subscription, is not allowed to operate. Cause value = 13 Roaming not allowed in this location area (Cause related to sub scription options) This cause is sent to an MS which requests location updating in a location area of a PLMN which offers roaming to that MS in that Location Ar ea, by subscription. Cause value = 14 GPRS services not allowed in this PLMN (Additional cause codes

for GMM) This cause is sent to the MS which requests GPRS service in a PLMN whic h does not offer roaming for GPRS services to that MS. Cause value = 15 No Suitable Cells In Location Area (Cause related to subscripti on options) This cause is sent to the MS if it requests location updating in a l ocation area where the MS, by subscription, is not allowed to operate, but when it should find another allowed location area in the same PLMN. NOTE: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to search for another allowed location area on the same PLMN. Cause No.16 "normal call clearing" (UMTS specific cause values for call control) This cause indicates that the call is being cleared because one of the users in volved in the call has requested that the call be cleared. Under normal situatio ns, the source of this cause is not the network. Cause value = 16 MSC temporarily not reachable (Additional cause codes for GMM) T his cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a PLMN where the MSC is temporarily not reachable via the GPRS part of the GSM network. Cause value = 17 Network failure (Causes related to PLMN specific network failures and congestion / Authentication Failures) This cause is sent to the MS if the M SC cannot service an MS generated request because of PLMN failures, e.g. problem s in MAP. Cause No.17 "user busy" (UMTS specific cause values for call control) This cause is 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. Cause No. 18 "no user responding" (UMTS specific cause values for call control) This cause is used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of ti me allocated (defined by the expiry of either timer T303 or T310). Cause No. 19 "user alerting, no answer" (UMTS specific cause values for call con trol) This cause is used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time. Cause value = 20 MAC failure (Causes related to PLMN specific network failures and congestion/Authentication Failures) This cause is sent to the network if the SI M detects that the MAC in the authentication request message is not fresh (see 3 GPP TS 33.102). Cause value = 21 Synch failure (Causes related to PLMN specific network failures a nd congestion/Authentication Failures) This cause is sent to the network if the SIM detects that the SQN in the authentication request message is out of range ( see 3GPP TS 33.102). Cause No. 21 "call rejected" (UMTS specific cause values for call control) This cause indicates that the equipment sending this cause does not wish to accept th is call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible. Cause No. 22 "number changed" (UMTS specific cause values for call control) This cause is returned to a calling mobile station when the called party number indi cated by the calling mobile station 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. Cause value = 22 Congestion (Causes related to PLMN specific network failures and c ongestion/Authentication Failures) This cause is sent if the service request can not be actioned because of congestion (e.g. no channel, facility busy/congested etc.). Cause value = 23 GSM authentication unacceptable (Causes related to PLMN specific n etwork failures and congestion/Authentication Failures) This cause is sent to th e network in UMTS if the MS supports the UMTS authentication algorithm and there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST me ssage. Cause No. 25 "pre-emption" (UMTS specific cause values for call control) This ca use is returned to the network when a mobile station clears an active call which is being pre-empted by another call with higher precedence.

Cause value = 25 LLC or SNDCP failure (GSM only) (GPRS specific cause values for s ession management) This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNS M-STATUS.request message with cause "DM received " or " invalid XID response ", see 3GPP TS 44.065 [78]) Cause value = 26 Insufficient resources (GPRS specific cause values for session m anagement) This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request or PD P context modification request cannot be accepted due to insufficient resources. Cause No. 26 "non-selected user clearing" (UMTS specific cause values for call c ontrol) Cause No. 27 "destination out of order" (UMTS specific cause values for call con trol) This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning co rrectly. The term "not functioning correctly" indicates that a signalling messag e was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc. Cause value = 27 Unknown or missing access point name (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because t he access point name was not included although required or if the access point n ame could not be resolved. Cause No. 28 "invalid number format (incomplete number)" (UMTS specific cause va lues for call control) This cause indicates that the called user cannot be reach ed because the called party number is not a valid format or is not complete. Cause value = 28 Unknown PDP address or PDP type (GPRS specific cause values for s ession management) This cause code is used by the network to indicate that the r equested service was rejected by the external packet data network because the PD P address or type could not be recognised. Cause No. 29 "facility rejected" (UMTS specific cause values for call control) T his cause is returned when a facility requested by user can not be provided by t he network. Cause value = 29 User authentication failed (GPRS specific cause values for sessio n management) This cause code is used by the network to indicate that the reques ted service was rejected by the external packet data network due to a failed use r authentication. Cause No. 30 "response to STATUS ENQUIRY" (UMTS specific cause values for call c ontrol) This cause is included in STATUS messages if the message is sent in resp onse to a STATUS ENQUIRY message. See also subclause 5.5.3. Cause value = 30 Activation rejected by GGSN (GPRS specific cause values for sessi on management) This cause code is used by the network to indicate that the reque sted service was rejected by the GGSN. Cause No. 31 "normal, unspecified" (UMTS specific cause values for call control) This cause is used to report a normal event only when no other cause in the nor mal class applies. Cause value = 31 Activation rejected, unspecified (GPRS specific cause values for session management) This cause code is used by the network to indicate that the requested service was rejected due to unspecified reasons. Cause value = 32 Service option not supported (GPRS specific cause values for sess ion management) This cause code is used by the network when the MS requests a se rvice which is not supported by the PLMN. Cause value = 33 Requested service option not subscribed (GPRS specific cause value s for session management) This cause is sent when the MS requests a service opti on for which it has no subscription. Cause No. 34 "no circuit/channel available" (Resource unavailable class) This ca use indicates that there is no appropriate circuit/channel presently available t o handle the call. Cause value = 34 Service option temporarily out of order (Causes related to nature of request) This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service

. Cause value = 35 NSAPI already used (GPRS specific cause values for session manage ment) This cause code may be used by a network to indicate that the NSAPI reques ted by the MS in the PDP context activation request is already used by another a ctive PDP context of this MS. Never to be sent, but can be received from a R97/R 98 network at PDP context activation Cause value = 36 Regular PDP context deactivation (GPRS specific cause values for session management) This cause code is used to indicate a regular MS or network initiated PDP context deactivation. Cause value = 37 QoS not accepted (GPRS specific cause values for session manageme nt) This cause code is used by the MS if the new QoS cannot be accepted that wer e indicated by the network in the PDP Context Modification procedure. Cause No. 38 "network out of order" (Resource unavailable class) 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. Cause value = 38 Call cannot be identified (Causes related to nature of request) This cause is sent when the network cannot identify the call associated with a c all re-establishment request. Cause value = 38 Network failure (GPRS specific cause values for session manage ment) This cause code is used by the network to indicate that the PDP context deactiva tion is caused by an error situation in the network. Cause value = 39 Reactivation requested (GPRS specific cause values for session management) This cause code is used by the network to request a PDP context reactivation aft er a GGSN restart. Cause value = 40 No PDP context activated (Additional cause codes for GMM) This cause is sent to the MS if the MS requests an establishment of the radio ac cess bearers for all active PDP contexts by sending a SERVICE REQUEST message in dicating "data" to the network, but the SGSN does not have any active PDP contex t(s). Cause value = 40 Feature not supported (GPRS specific cause values for session m anagement) This cause code is used by the MS to indicate that the PDP context activation in itiated by the network is not supported by the MS. Cause No. 41 "temporary failure" (Resource unavailable class) 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 mobile station may wish to try another call attempt almost immediately. Cause value = 41 semantic error in the TFT operation. (GPRS specific cause value s for session management) This cause code is used by the network to indicate that the there is a semantic error in the TFT operation included in a secondary PDP context activation reques t or an MS-initiated PDP context modification. Cause No. 42 "switching equipment congestion" (Resource unavailable class) This cause indicates that the switching equipment generating this cause is exper iencing a period of high traffic. Cause value = 42 syntactical error in the TFT operation. (GPRS specific cause va lues for session management) This cause code is used by the network to indicate that there is a syntactical e rror in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification. Cause No. 43 "access information discarded" (Resource unavailable class) This cause indicates that the network could not deliver access information to th e remote user as requested; i.e., a user-to-user information, low layer compatib ility, high layer compatibility, or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optional ly included in the diagnostic. Cause value = 43 unknown PDP context (GPRS specific cause values for session man

agement) This cause code is used by the network to indicate that the PDP context identifi ed by the Linked TI IE the secondary PDP context activation request is not activ e. Cause No. 44 "requested circuit/channel not available" (Resource unavailable cla ss) This cause is returned when the circuit or channel indicated by the requesting e ntity cannot be provided by the other side of the interface. Cause value = 44 semantic errors in packet filter(s) (GPRS specific cause values for session management) This cause code is used by the network to indicate that there is one or more sem antic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification. Cause value = 45 syntactical error in packet filter(s) (GPRS specific cause valu es for session management) This cause code is used by the network to indicate that there is one or more syn tactical errors in packet filter(s) of the TFT included in a secondary PDP conte xt activation request or an MS-initiated PDP context modification. Cause value = 46 PDP context without TFT already activated (GPRS specific cause values for session management) This cause code is used by the network to indicate that the network has already activated a PDP context without TFT. Cause No. 47 "resource unavailable, unspecified" (Resource unavailable class) This cause is used to report a resource unavailable event only when no other cau se in the resource unavailable class applies. Cause No. 49 "quality of service unavailable" (Service or option not available c lass) This cause indicates to the mobile station that the requested quality of service , as defined in ITU-T Recommendation X.213, cannot be provided. Cause No. 50 "Requested facility not subscribed" (Service or option not availabl e class) This cause indicates that the requested supplementary service could not be provi ded by the network because the user has no completed the necessary administrativ e arrangements with its supporting networks. Cause No. 55 "Incoming calls barred within the CUG" (Service or option not avail able class) This cause indicates that although the called party is a member of the CUG for t he incoming CUG call, incoming calls are not allowed within this CUG. Cause No. 57 "bearer capability not authorized" (Service or option not available class) This cause indicates that the mobile station has requested a bearer capability w hich is implemented by the equipment which generated this cause but the mobile s tation is not authorized to use. Cause No. 58 "bearer capability not presently available" (Service or option not available class) This cause indicates that the mobile station has requested a bearer capability w hich is implemented by the equipment which generated this cause but which is not available at this time. Cause No. 63 "service or option not available, unspecified" (Service or option n ot available class) This cause is used to report a service or option not available event only when n o other cause in the service or option not available class applies. Cause No. 68 "ACM equal to or greater than ACMmax" (Service or option not availa ble class) This cause is used by the mobile to indicate that call clearing is due to ACM be ing greater than or equal to ACMmax. Cause No. 65 "bearer service not implemented" (Service or option not implemented class) This cause indicates that the equipment sending this cause does not support the bearer capability requested.

Cause No. 69 "Requested facility not implemented" (Service or option not impleme nted class) This cause indicates that the equipment sending this cause does not support the requested supplementary service. Cause No. 70 "only restricted digital information bearer capability is available " (Service or option not implemented class) This cause indicates that one equipment has requested an unrestricted bearer ser vice, but that the equipment sending this cause only supports the restricted ver sion of the requested bearer capability. Cause No. 79 "service or option not implemented, unspecified" (Service or option not implemented class) 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. Cause No. 81 "invalid transaction identifier value" (Service or option not imple mented class) This cause indicates that the equipment sending this cause has received a messag e with a transaction identifier which is not currently in use on the MS-network interface. Cause No. 87 "user not member of CUG" (Service or option not implemented class) This cause indicates that the called user for the incoming CUG call is not a mem ber of the specified CUG. Cause No. 88 "incompatible destination" (Service or option not implemented class ) This cause indicates that the equipment sending this cause has received a reques t to establish a call which has low layer compatibility, high layer compatibilit y, or other compatibility attributes (e.g., data rate) which cannot be accommoda ted. Cause No. 91 "invalid transit network selection" (Service or option not implemen ted class) Cause No. 95 "semantically incorrect message" (Causes related to invalid message s) This cause is used to report receipt of a message with semantically incorrect co ntents (see subclause 8.8). Cause No. 96 "invalid mandatory information" (Causes related to invalid messages ) This cause indicates that the equipment sending this cause has received a messag e with a non-semantical mandatory IE error (see subclause 8.5). Cause No. 96 "invalid mandatory information" (Causes related to invalid messages ) Cause No. 97 "message type non-existent or not implemented" (Causes related to i nvalid messages) This cause indicates that the equipment sending this cause has received a messag e 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. Cause No. 97 "message type non-existent or not implemented" (Causes related to i nvalid messages) This cause indicates that the equipment sending this cause has received a messag e 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. Cause No. 98 "message type not compatible with protocol state" (Causes related t o invalid messages) This cause indicates that the equipment sending this cause has received a messag e not compatible with the protocol state (subclause 8.4). Cause No. 98 "message type not compatible with protocol state" (Causes related t o invalid messages) This cause indicates that the equipment sending this cause has received a messag e not compatible with the protocol state. Cause No. 99 "information element non-existent or not implemented" (Causes relat ed to invalid messages) This cause indicates that the equipment sending this cause has received a messag

e which includes information elements not recognized because the information ele ment identifier is not defined or it is defined but not implemented by the equip ment sending the cause. However, the information element is not required to be p resent in the message in order for the equipment sending the cause to process th e message. Cause No. 100 "conditional IE error" (Causes related to invalid messages) This cause indicates that the equipment sending this cause has received a messag e with conditional IE errors (see subclause 8.7.2). Cause No. 101 "message not compatible with protocol state" (Causes related to in valid messages) This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an inc ompatible call state. Cause No. 102 "recovery on timer expiry" This cause indicates that a procedure has been initiated by the expiry of a time r in association with 3GPP TS 24.008 error handling procedures. Cause No. 111 "protocol error, unspecified" (Causes related to invalid messages) This cause is used to report a protocol error event only when no other cause in the protocol error class applies. 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 w hich is being sent cannot be ascertained Events in event log event list .