**************************UE TRACE PARSER FUNCTION AND ITS IMPORTANCE

******************************************

- gsh add_ms_noclist -imsi 624017509354190 -hours 900

- gsh create_ue_trace -id 624017509354190 -type imsi -ref 121155151515 -ifl all
-iflm all -ip NULL
-then you check config

- gsh check_config
-then activate
- gsh activate_config_pending (first list_config_pending to be sure you are the
only one working on the node)
-then now *uetracer_parser.pl -i 624017509354190

**************************************************************************8

********************Integrated Traffic Capture per interface

******************************************8888

- === HQSGSN02 aristide@eqm01s09p2 ANCB ~ # gsh action_itc_job_start -jn S1-MME //

depending of the interface you wanna capture.
- then wait sometime.
-Then stop first: === HQSGSN02 aristide@eqm01s09p2 ANCB ~ # gsh action_itc_job_stop
-jn S1-MME

- then wait some time

- then save now: HQSGSN02 aristide@eqm01s09p2 ANCB ~ # gsh action_itc_job_save -jn
S1-MME
- Now you can fetch the result and analyse.
- Please dear...

read also the alex of that one.

Please write it down somewhere as well

********************************************************************8

PDP Activation failed Possible Root Cause

posted Apr 4, 2012, 10:05 PM by Aswadi Abdul Rahman
"No resources available" indicates that not enough resources are available within
the network to allow the PDP Context to be created.

"Missing or unknown APN" indicates e.g. when the GGSN does not support the Access
Point Name.

"Unknown PDP address or PDP type" indicates when the GGSN does not support the PDP
type or the PDP address.

"User authentication failed" indicates that the external packet network has
rejected the service requested by the user e.g. the authentication check in the
RADIUS server failed.

"PDP context without TFT already activated" indicates that a PDP context has
already been activated without a TFT for that MS.

"Context not found" indicates that a Create PDP Request for a subsequent PDP
context has been received, but the PDP context associated with the request, which
the SGSN believes to be active does not exist on the GGSN.

"APN access denied � no subscription" indicates that the GGSN has denied the user
access to an APN because a subscription is required, but the subscriber does not
have the necessary subscription.

"New PDP type due to network preference" indicates that the GGSN has selected a PDP
type different from the one sent by the MS.

"New PDP type due to single address bearer only" indicates that the MS has
requested PDP type IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN
but the Dual Address Bearer Flag bit of the Common Flags IE is set to 0 or the
Common Flags IE is absent, or only single IP version addressing is possible in the
PDN.

***********************************************8
PDP Activation Failed due to Core

Cause value

Cause

192

Non-existent

193

Invalid message format

194

IMSI not known

195

MS is GPRS Detached

196

MS is not GPRS Responding

197

MS Refuses

198

Version not supported

199

No resources available
200

Service not supported

201

Mandatory IE incorrect

202

Mandatory IE missing

203

Optional IE incorrect

204

System failure

205

Roaming restriction

206

P-TMSI Signature mismatch

207

GPRS connection suspended

208

Authentication failure

209

User authentication failed

210

Context not found

211

All dynamic PDP addresses are occupied

212

No memory is available

213

Relocation failure

214
Unknown mandatory extension header

215

Semantic error in the TFT operation

216

Syntactic error in the TFT operation

217

Semantic errors in packet filter(s)

218

Syntactic errors in packet filter(s)

219

Missing or unknown APN

220

Unknown PDP address or PDP type

221

PDP context without TFT already activated

222

APN access denied � no subscription

223

APN Restriction type incompatibility withcurrently active PDP Contexts

224

MS MBMS Capabilities Insufficient

225

Invalid Correlation-ID

226

MBMS Bearer Context Superseded

************************************************************

PDP Activation Failed due to RAN

Cause value

Cause

25
LLC or SNDCP Failure

26

Insufficient Resources

27

Missing or Unknown APN

28

Unknown PDP Address or PDP Type

29

User Authentication Failed

30

Activation Rejected By GGSN

31

Activation Rejected, Unspecified

32

Service Option Not Supported

33

Requested Service Opt Not Subscribed

34

Service Opt Temporarily Out of Order

35

NSAPI Already Used

36

Regular Deactivation

37

QoS Not Accepted

38

Network Failure

39

Reactivation Required
40

Feature Not Supported

41

Semantic Error in TFT Operation

42

Syntactical Error in TFT Operation

43

Unknown PDP Context

44

Semantic Error in Packet Filter(s)

45

Syntactical Error inPacket Filter(s)

46

PDP Context Without TFT Already Activated

81

Invalid Transaction Identifier Value

95

Semantically Incorrect Message

96

Invalid Mandatory Information

97

Msg Type Non-existent/Non ImplementedState

98

Msg Type Not Compatible With Protocol State

99

IE Non-existent or Not Implemented

100

Conditional IE Error

101

Msg Not Compatible With Protocol State

111

Protocol Error, Unspecified

112

APN Restrict Value Incompatible Without PDP Context

***************************************************************8

RAB Assignment Cause Code Common Reason

Below are the common issue behind all the root cause.

Radio Network Layer cause

Meaning

Deciphering Keys Not Available

The action failed because RNC is not able to provide requested deciphering keys.

Conflict with already existing Integrity protection and/or Ciphering information

The action was not performed due to that the requested security mode configuration
was in conflict with the already existing security mode configuration.

Condition Violation For Guaranteed Bit Rate

The action was not performed due to condition violation for guaranteed bit rate.

Condition Violation For SDU Parameters

The action was not performed due to condition violation for SDU parameters.

Condition Violation For Traffic Handling Priority

The action was not performed due to condition violation for traffic handling
priority.

Dedicated Assistance data Not Available

The action failed because RNC is not able to successfully deliver the requested
dedicated assistance data to the UE.

Directed Retry

The reason for action is Directed Retry

Failure In The Radio Interface Procedure

Radio interface procedure has failed.

Incoming Relocation Not Supported Due To PUESBINE Feature

The incoming relocation cannot be accepted by the target RNC because of the
PUESBINE feature.
Interaction With Other Procedure

Relocation was cancelled due to interaction with other procedure.

Invalid RAB ID

The action failed because the RAB ID is unknown in the RNC.

Invalid RAB Parameters Combination

The action failed due to invalid RAB parameters combination.

Invalid RAB Parameters Value

The action failed due to invalid RAB parameters value.

Iu UP Failure

The action failed due to Iu UP failure.

No remaining RAB

The reason for the action is no remaining RAB.

RAB Pre-empted

The reason for the action is that RAB is pre-empted.

Radio Connection With UE Lost

The action is requested due to losing radio connection to the UE

Release Due To UE Generated Signalling Connection Release

Release requested due to UE generated signalling connection release.

Release Due To UTRAN Generated Reason

Release is initiated due to UTRAN generated reason.

Relocation Cancelled

The reason for the action is relocation cancellation.

Relocation Desirable for Radio Reasons

The reason for requesting relocation is radio related.

Relocation Failure In Target CN/RNC Or Target System

Relocation failed due to a failure in target CN/RNC or target system.

Relocation Not Supported In Target RNC Or Target System

Relocation failed because relocation was not supported in target RNC or target
system.

Relocation Target not allowed

Relocation to the indicated target cell is not allowed for the UE in question.

Relocation Triggered

The action failed due to relocation.

Repeated Integrity Checking Failure

The action is requested due to repeated failure in integrity checking.

Request Superseded

The action failed because there was a second request on the same RAB.

Requested Ciphering And/Or Integrity Protection Algorithms Not Supported

The UTRAN or the UE is unable to support the requested ciphering and/or integrity
protection algorithms.

Requested Guaranteed Bit Rate For DL Not Available

The action failed because requested guaranteed bit rate for DL is not available.

Requested Guaranteed Bit Rate For UL Not Available

The action failed because requested guaranteed bit rate for UL is not available.

Requested Guaranteed Bit Rate Not Available

The action failed because requested guaranteed bit rate is not available.

Requested Information Not Available

The action failed because requested information is not available.

Requested Maximum Bit Rate For DL Not Available

The action failed because requested maximum bit rate for DL is not available.

Requested Maximum Bit Rate For UL Not Available

The action failed because requested maximum bit rate for UL is not available.

Requested Maximum Bit Rate Not Available

The action failed because requested maximum bit rate is not available.

Requested Request Type Not Supported

The RNC is not supporting the requested location request type either because it
doesn�t support the requested event or it doesn�t support the requested report
area.

Location Reporting Congestion

The action was not performed due to an inability to support location reporting
caused by overload.
Requested Traffic Class Not Available

The action failed because requested traffic class is not available.

Requested Transfer Delay Not Achievable

The action failed because requested transfer delay is not achievable.

Resource Optimisation Relocation

The reason for requesting relocation is resource optimisation.

Successful Relocation

The reason for the action is completion of successful relocation.

Time Critical Relocation

Relocation is requested for time critical reason i.e. this cause value is reserved
to represent all critical cases where the connection is likely to be dropped if
relocation is not performed.

TQUEUING Expiry

The action failed due to expiry of the timer TQUEUING.

TRELOCalloc Expiry

Relocation Resource Allocation procedure failed due to expiry of the timer

TRELOCalloc.

TRELOCcomplete Expiry

The reason for the action is expiry of timer TRELOCcomplete.

TRELOCoverall Expiry

The reason for the action is expiry of timer TRELOCoverall.

TRELOCprep Expiry

Relocation Preparation procedure is cancelled when timer TRELOCprep expires.

Unable To Establish During Relocation

RAB failed to establish during relocation because it cannot be supported in the

target RNC or the RAB did not exist in the source RNC.

Unknown Target RNC

Relocation rejected because the target RNC is not known to the CN.

User Inactivity

The action is requested due to user inactivity on one or several non real time RABs
e.g. in order to optimise radio resource.

User Plane Versions Not Supported

The action failed because requested user plane versions were not supported.

RNC unable to establish all RFCs

RNC couldn�t establish all RAB subflow combinations indicated within the RAB
Parameters IE.

Reduce Load in Serving Cell

Load on serving cell needs to be reduced.

No Radio Resources Available in Target Cell

Load on target cell is too high.

GERAN Iu-mode failure

The RAB establishment/modification/relocation failed because the GERAN BSC cannot

provide an appropriate RAB due to limited capabilities within GERAN.

Access Restricted Due to Shared Networks

Access is not permitted in the cell due to Shared Networks.

Traffic Load In The Target Cell Higher Than In The Source Cell

Relocation to reduce load in the source cell is rejected, as the target cell�s
traffic load is higher than that in the source cell.

MBMS - No Multicast Service For This UE

The request for the Multicase Service list of one UE was not fulfilled because the
UE does not have any active multicast service.

MBMS - Unknown UE ID

The request for the Multicase Service list of one UE was not fulfilled because the
CN does not know the UE.

Successful MBMS Session Start - No Data Bearer Necessary

The MBMS Session Start procedure was successfully performed, but the RNC does not
have any interested UE.

MBMS - Superseded Due To NNSF

The MBMS Session Start procedure was rejected because of successful operation
towards another CN node.

MBMS - UE Linking Already Done

The UE linking failed, because the UE has already been linked to the given
Multicast service.

MBMS - UE De-Linking Failure - No Existing UE Linking

The UE de-linking failed, because the UE had not been linked to the given Multicast
service.
TMGI Unknown

The requested MBMS action failed because the indicated TMGI is unknown.

Successful MBMS Session Start � IP Multicast Bearer established

The RNC was able to join the indicated IP Multicast Group.

Radio Network Layer cause extension

Meaning

IP Multicast Address And APN Not Valid

The MBMS registration failed because the IP Multicast Address and APN are not
valid.

MBMS De-Registration Rejected Due To Implicit Registration

The MBMS De-registration was rejected because of implicit registration.

MBMS - Request Superseded

The MBMS Registration or De-registration was superseded due to another ongoing

procedure.

MBMS De-Registration During Session Not Allowed

The MBMS De-registration is not allowed during the MBMS session.

MBMS - No Data Bearer Necessary

The RNC no longer have any UEs interested in the MBMS data bearer.

Periodic Location Information not Available

No UE position estimate was available when the periodic report was triggered.

GTP Resources Unavailable

The RNC initiates RAB Release Request procedure with this error cause value if it
received a GTP-U error indication.

TMGI in Use and overlapping MBMS Service Area

The RNC has an MBMS Session up and running with that TMGI, a parallel MBMS session
with the same TMGI in another overlapping MBMS Service Area is not allowed.

MBMS - No Cell in MBMS Service Area

The RNC does not have any cell of the indicated MBMS Service Area.

No Iu CS UP relocation

The relocation is triggered by CS call and the source RNC has no Iu CS user plane.

CS Fallback triggered
The relocation was triggered for CS Fallback reason at the source side.

Invalid CSG Id

The CSG ID provided to the target UTRAN was found invalid.

Transport Layer cause

Meaning

Iu Transport Connection Failed to Establish

The action failed because the Iu Transport Network Layer connection could not be
established.

Signalling Transport Resource Failure

Signalling transport resources have failed (e.g. processor reset).

NAS cause

Meaning

Normal Release

The release is normal.

User Restriction Start Indication

A location report is generated due to entering a classified area set by O&M.

User Restriction End Indication

A location report is generated due to leaving a classified area set by O&M.

CSG Subscription Expiry

The action is due to the UE becoming a non-member of the currently used CSG.

Protocol cause: Meaning

Abstract Syntax Error (Reject): The received message included an abstract syntax
error and the concerning criticality indicated "reject".

Abstract Syntax Error (Ignore And Notify): The received message included an
abstract syntax error and the concerning criticality indicated "ignore and notify".

Abstract Syntax Error (Falsely Constructed Message): The received message contained
IEs or IE groups in wrong order or with too many occurrences.

Message Not Compatible With Receiver State: The received message was not compatible
with the receiver state.
Semantic Error: The received message included a semantic error.

Transfer Syntax Error: The received message included a transfer syntax error.

Miscellaneous cause /// Meaning

Network Optimisation: The action is performed for network optimisation.

No Resource Available: No requested resource is available.

O&M Intervention: The action is due to O&M intervention.

Unspecified Failure:Sent when none of the specified cause values applies.

***********************************************************************************
*******************

GPRS specific cause values for GPRS Session Management

posted Dec 8, 2011, 2:36 AM by Aswadi Abdul

I.1 Causes related to nature of request

Cause value = 8 Operator Determined Barring

This cause code is used by the network to indicate that the requested service was
rejected by the SGSN due to Operator Determined Barring.

Cause value = 24 MBMS bearer capabilities insufficient for the service

This cause code is used by the network to indicate that an MBMS context activation
request was rejected by the network, because the MBMS bearer capabilities are
insufficient for the MBMS service.

Cause value = 25 LLC or SNDCP failure (A/Gb mode only)

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 SNSM-STATUS.request
message with cause "DM received " or " invalid XID response ", see 3GPP TS 44.065
[78])

Cause value = 26 Insufficient resources

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, PDP context
modification request, or MBMS context activation request cannot be accepted due to
insufficient resources.

Cause value = 27 Unknown or missing access point name

This cause code is used by the network to indicate that the requested service was
rejected by the external packet data network because the access point name was not
included although required or if the access point name could not be resolved.

Cause value = 28 Unknown PDP address or PDP type

This cause code is used by the network to indicate that the requested service was
rejected by the external packet data network because the PDP address or type could
not be recognised.

Cause value = 29 User authentication failed

This cause code is used by the network to indicate that the requested service was
rejected by the external packet data network due to a failed user authentication.

Cause value = 30 Activation rejected by GGSN, Serving GW or PDN GW

This cause code is used by the network to indicate that the requested service was
rejected by the GGSN, Serving GW or PDN GW.

Cause value = 31 Activation rejected, unspecified

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

This cause code is used by the network when the MS requests a service which is not
supported by the PLMN.

Cause value = 33 Requested service option not subscribed

See Annex G, clause 4.

Cause value = 34 Service option temporarily out of order

See Annex G, clause 4.

Cause value = 35 NSAPI already used

This cause code may be used by a network to indicate that the NSAPI requested by
the MS in the PDP context activation request is already used by another active PDP
context of this MS.

Never to be sent, but can be received from a R97/R98 network at PDP context
activation

Cause value = 36 Regular deactivation

This cause code is used to indicate a regular MS or network initiated PDP context
deactivation or a regular network initiated MBMS context deactivation.

Cause value = 37 QoS not accepted

This cause code is used by the MS if the new QoS cannot be accepted that were
indicated by the network in the PDP Context Modification procedure.

Cause value = 38 Network failure

This cause code is used by the network to indicate that the PDP context
deactivation or the MBMS context deactivation is caused by an error situation in
the network.

Cause value = 39 Reactivation requested

This cause code is used by the network to request a PDP context reactivation after
a GGSN restart.

Cause value = 40 Feature not supported

This cause code is used by the MS to indicate that the PDP context activation or
the MBMS context activation initiated by the network is not supported by the MS.

Cause value = 41 semantic error in the TFT operation.

This cause code is used by the network or the MS to indicate that there is a
semantic error in the TFT operation included in a secondary PDP context activation
request or an MS-initiated PDP context modification or a network requested
secondary PDP context activation.

Cause value = 42 syntactical error in the TFT operation.

This cause code is used by the network or the MS to indicate that there is a
syntactical error in the TFT operation included in a secondary PDP context
activation request or an MS-initiated PDP context modification or a network
requested secondary PDP context activation.

Cause value = 43 unknown PDP context

This cause code is used by the network or the MS to indicate that the PDP context
identified by the Linked TI IE in the secondary PDP context activation request or a
network requested secondary PDP context activation is not active.

Cause value = 44 semantic errors in packet filter(s)

This cause code is used by the network or the MS to indicate that there is one or
more semantic errors in packet filter(s) of the TFT included in a secondary PDP
context activation request or an MS-initiated PDP context modification or a network
requested secondary PDP context activation.

Cause value = 45 syntactical error in packet filter(s)

This cause code is used by the network or the MS to indicate that there is one or
more syntactical errors in packet filter(s) of the TFT included in a secondary PDP
context activation request or an MS-initiated PDP context modification or a network
requested secondary PDP context activation.

Cause value = 46 PDP context without TFT already activated

This cause code is used by the network or the MS to indicate that it has already
activated a PDP context without TFT.

Cause value = 47 Multicast group membership time-out

This cause code is used by the network to indicate that the MBMS context is
deactivated because the timer supervising the IGMP group membership interval (see
RFC 3376 [107], subclause 8.4) or the MLD multicast listener interval (see RFC 2710
[108], subclause 7.4) expired.

Cause value = 48 Activation rejected, B earerC ontrolMode violation

This cause code is used by the network or the MS to indicate that the requested
service was rejected because of Bearer Control Mode violation.

Cause value = 50 PDP type IPv4 only allowed

This cause is used by the network to indicate that the requested PDN connectivity
is accepted with the restriction that only PDP type IPv4 is allowed.

Cause value = 51 PDP type IPv6 only allowed

This cause is used by the network to indicate that the requested PDN connectivity
is accepted with the restriction that only PDP type IPv6 is allowed.

Cause value = 52 single address bearers only allowed

This cause is used by the network to indicate that the requested PDN connectivity
is accepted with the restriction that only single IP version bearers are allowed.

Cause value = 56 Collision with network initiated request.

This cause code is used by the network to indicate that the MS-initiated request
was rejected since the network has requested a secondary PDP context activation for
the same service using a network-initiated procedure.

Cause value = 112 APN restriction value incompatible with active PDP context.
This cause code is used by the network to indicate that the PDP context(s) or MBMS
context(s) have an APN restriction value that is not allowed in combination with a
currently active PDP context. Restriction values are defined in 3GPP TS 23.060
[74], subclause 15.4.

I.2 Causes related to invalid messages

Cause value = 81 Invalid transaction identifier value.
See annex H, subclause H.5.1.

Cause value = 95 Semantically incorrect message.

See annex H, subclause H.5.5.

Cause value = 96 Invalid mandatory information.

See annex H, subclause H.6.1.

Cause value = 97 Message type non-existent or not implemented.

See annex H, subclause H.6.2.

Cause value = 98 Message not compatible with protocol state.

See annex H, subclause H.6.3.

Cause value = 99 Information element non-existent or not implemented.

See annex H, subclause H.6.4.

Cause value = 100 Conditional IE error.

See annex H, subclause H.6.5.

Cause value = 101 Message not compatible with protocol state.

See annex H, subclause H.6.6.

Cause value = 111 Protocol error, unspecified.

See annex H, subclause H.6.8.

***********************************************************************************
****************88
3GPP spesific cause value for mobility management (packet)

In here are all the PDP reject response message. I'm just take the Packet portion
since that is the world that i'm currently in.

G.1 Causes related to MS identification

Cause value = 2 IMSI unknown in HLR

This cause is sent to the MS if the MS is not known (registered) in the HLR. This
cause code does not affect operation of the GPRS service, although is may be used
by a GMM procedure.

Cause value = 3 Illegal MS

This cause is sent to the MS when the network refuses service to the MS either
because an identity of the MS is not acceptable to the network or because the MS
does not pass the authentication check, i.e. the SRES received from the MS is
different from that generated by the network. When used by an MM procedure, except
the authentication procedure, this cause does not affect operation of the GPRS
service.

Cause value = 4 IMSI unknown in VLR

This cause is sent to the MS when the given IMSI is not known at the VLR.

Cause value = 5 IMEI not accepted

This cause is sent to the MS if the network does not accept emergency call
establishment using an IMEI or not accept attach procedure for emergency services
using an IMEI.
Cause value = 6 Illegal ME
This cause is sent 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.

G.2 Cause related to subscription options

Cause value = 11 PLMN not allowed

This cause 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

This cause is sent to the MS if it requests location updating in a location area
where the HPLMN determines that the MS, by subscription, is not allowed to operate.

NOTE: If cause #12 is sent to a roaming subscriber the subscriber is denied service
even if other PLMNs are available on which registration was possible.

Cause value = 13 Roaming not allowed in this location area

This cause is sent to an MS which requests location updating in a location area of
a PLMN which by subscription offers roaming to that MS but not in that Location
Area.

Cause value = 15 No Suitable Cells In Location Area

This cause is sent to the MS if it requests location updating in a location 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 value = 25 Not authorized for this CSG

This cause is sent to the MS if it requests access in a CSG cell where the MS
either has no subscription to operate or the MS's subscription has expired and it
should find another cell in the same PLMN.

NOTE: The MS not supporting CSG will not receive cause# 25, as such a MS is not
supposed to try to access a CSG cell.

G.3 Causes related to PLMN specific network failures and congestion/Authentication

Failures

Cause value = 20 MAC failure

This cause is sent to the network if the USIM detects that the MAC in the
AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is not fresh
(see 3GPP TS 33.102 [5a]).

Cause value = 21 Synch failure

This cause is sent to the network if the USIM detects that the SQN in the
AUTHENTICATION REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is out of
range (see 3GPP TS 33.102 [5a]).

Cause value = 17 Network failure

This cause is sent to the MS if the MSC cannot service an MS generated request
because of PLMN failures, e.g. problems in MAP.

Cause value = 22 Congestion

This cause is sent if the service request cannot be actioned because of congestion
(e.g. no channel, facility busy/congested etc.).

Cause value = 23 GSM authentication unacceptable

This cause is sent to the network in Iu mode if a USIM is inserted in the MS and
there is no Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST
or AUTHENTICATION_AND_CIPHERING REQUEST message.

G.4 Causes related to nature of request

Cause value = 32 Service option not supported

This cause is sent when the MS requests a service/facility in the CM SERVICE
REQUEST message which is not supported by the PLMN.

Cause value = 33 Requested service option not subscribed

This cause is sent when the MS requests a service option for which it has no
subscription.

Cause value = 34 Service option temporarily out of order

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 = 38 Call cannot be identified

This cause is sent when the network cannot identify the call associated with a call
re-establishment request.

G.5 Causes related to invalid messages

Cause value = 95 Semantically incorrect message.

See annex H, subclause H.5.10.

Cause value = 96 Invalid mandatory information.

See annex H, subclause H.6.1.

Cause value = 97 Message type non-existent or not implemented.

See annex H, subclause H.6.2.

Cause value = 98 Message not compatible with protocol state.

See annex H, subclause H.6.3.

Cause value = 99 Information element non-existent or not implemented.

See annex H, subclause H.6.4.

Cause value = 100 Conditional IE error.

See annex H, subclause H.6.5.

Cause value = 101 Message not compatible with protocol state.

See annex H, subclause H.6.6.

Cause value = 111 Protocol error, unspecified.

See annex H, subclause H.6.8.

G.6 Additional cause codes for GMM

Cause value = 7 GPRS services not allowed
This cause is sent to the MS when it is not allowed to operate GPRS services.

Cause value = 8 GPRS services and non-GPRS services not allowed

This cause is sent to the MS when it is not allowed to operate either GPRS or non-
GPRS services.

Cause value = 9 MS identity cannot be derived by the network

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

This cause is sent to the MS either if the network has implicitly detached the MS,
e.g. some while after the Mobile reachable timer has expired, or if the GMM context
data related to the subscription dose not exist in the SGSN e.g. because of a SGSN
restart.

Cause value = 14 GPRS services not allowed in this PLMN

This cause is sent to the MS which requests GPRS service in a PLMN which does not
offer roaming for GPRS services to that MS.

Cause value = 16 MSC temporarily not reachable

This 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 network.

Cause value = 40 No PDP context activated

This cause is sent to the MS if the MS requests an establishment of the radio
access bearers for all active PDP contexts by sending a SERVICE REQUEST message
indicating "data" to the network, but the SGSN does not have any active PDP
context(s).

***********************************************************************************
***************888

3GPP specific cause values for call control

This is just extension from 3GPP specific cause value for mobility management
(packet) . They seems connected somehow.

H.1 Normal class

H.1.1 Cause No. 1 "unassigned (unallocated) number"

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 currently
assigned (allocated).

H.1.2 Cause No. 3 "no route to destination"

This cause indicates that the called user cannot be reached because the network
through which the call has been routed does not serve the destination desired.

H.1.3 Cause No. 6 "channel unacceptable"

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

H.1.4 Cause No. 8 "operator determined barring"

This cause indicates that the MS has tried to access a service that the MS's
network operator or service provider is not prepared to allow.

H.1.5 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.

H.1.6 Cause No.17 "user busy"

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.

H.1.7 Cause No. 18 "no user responding"

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 time
allocated (defined by the expiry of either timer T303 or T310).

H.1.8 Cause No. 19 "user alerting, no answer"

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.

H.1.9 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.

H.1.10 Cause No. 22 "number changed"

This cause is returned to a calling mobile station when the called party number
indicated 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.

H.1.11 Cause No. 25 "pre-emption"

This cause is returned to the network when a mobile station clears an active call
which is being pre-empted by another call with higher precedence.

H.1.12 Cause No. 26 "non-selected user clearing"

Not supported. Treated as cause no. 31.

H.1.13 Cause No. 27 "destination out of order"

This cause indicates that the destination indicated by the mobile station 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 user; e.g., a physical layer or data link layer failure
at the remote user, user equipment off-line, etc.

H.1.14 Cause No. 28 "invalid number format (incomplete number)"

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

H.1.15 Cause No. 29 "facility rejected"

This cause is returned when a facility requested by user can not be provided by the
network.

H.1.16 Cause No. 30 "response to STATUS ENQUIRY"

This cause is included in STATUS messages if the message is sent in response to a
STATUS ENQUIRY message. See also subclause 5.5.3.
H.1.17 Cause No. 31 "normal, unspecified"
This cause is used to report a normal event only when no other cause in the normal
class applies.

H.2 Resource unavailable class

H.2.1 Cause No. 34 "no circuit/channel available"

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

H.2.2 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.

H.2.3 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 mobile station may
wish to try another call attempt almost immediately.

H.2.4 Cause No. 42 "switching equipment congestion"

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

H.2.5 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., a 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.

H.2.6 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.

H.2.7 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.

H.3 Service or option not available class

H.3.1 Cause No. 49 "quality of service unavailable"

This cause indicates to the mobile station that the requested quality of service,
as defined in ITU-T Recommendation X.213, cannot be provided.

H.3.2 Cause No. 50 "Requested facility not subscribed"

This cause indicates that the requested supplementary service could not be provided
by the network because the user has no completed the necessary administrative
arrangements with its supporting networks.

H.3.3 Cause No. 55 "Incoming calls barred within the 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 within this CUG.

H.3.4 Cause No. 57 "bearer capability not authorized"

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

H.3.5 Cause No. 58 "bearer capability not presently available"

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

H.3.6 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.

H.3.7 Cause No. 68 "ACM equal to or greater than ACMmax"

This cause is used by the mobile to indicate that call clearing is due to ACM being
greater than or equal to ACMmax.

H.4 Service or option not implemented class

H.4.1 Cause No. 65 "bearer service not implemented"

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

H.4.2 Cause No. 69 "Requested facility not implemented"

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

H.4.3 Cause No. 70 "only restricted digital information bearer capability is

available"
This cause indicates that one equipment has requested an unrestricted bearer
service, but that the equipment sending this cause only supports the restricted
version of the requested bearer capability.

H.4.4 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.

H.5 Invalid message (e.g., parameter out of range) class

H.5.1 Cause No. 81 "invalid transaction identifier value"

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

H.5.2 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.

H.5.3 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.

H.5.4 Cause No. 91 "invalid transit network selection"

For further study. Treated as cause no. 95.

H.5.5 Cause No. 95 "semantically incorrect message"

This cause is used to report receipt of a message with semantically incorrect
contents (see subclause 8.8).

H.6 Protocol error (e.g., unknown message) class

H.6.1 Cause No. 96 "invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message
with a non-semantical mandatory IE error (see subclause 8.5).

H.6.2 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.

H.6.3 Cause No. 98 "message type not compatible with protocol state"
This cause indicates that the equipment sending this cause has received a message
not compatible with the protocol state (subclause 8.4).

H.6.4 Cause No. 99 "information element non-existent or not implemented"

This cause indicates that the equipment sending this cause has received a message
which 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.

H.6.5 Cause No. 100 "conditional IE error"

This cause indicates that the equipment sending this cause has received a message
with conditional IE errors (see subclause 8.7.2).

H.6.6 Cause No. 101 "message not compatible with protocol state"
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
incompatible call state.

H.6.7 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 3GPP TS 24.008 error handling procedures.

H.6.8 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.

H.7 Interworking class

H.7.1 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.

Reference:
Mobile radio interface Layer 3 specification(3GPP TS 24.008)

*********************To drill down Session and Mobility Event cause codes use the
log files descrived below**********
EBM log, EPG persistent logs, MS tools, SGSN extended UE trace as well
U have to read traces or logs as I said earlier. Didn�t u see this message ?
And add mm/sm/event/auth logs
MME, EPG, Smartcare Back End DB.
Case handled.

Root cause : Wrong provisioning done.

Summary:
Users impacted were provisioned with APN 28 while they are postpaid users.
Therefore, they were not able to use their dedicated APN (APN 25, PDPCP-2) to reach
M2M offer.

Recommendation:
In case APN is not present on HLR, DON�T Request to activate any other APN,
particularly while the PDPCP parameter is already present. Otherwise, this will
lead to new inconsistencies on HLR and issue as noticeable.

PS : PDPCP-1 is for prepaid (same as APN 28), and PDPCP-2 is for postpaid (same as
APN 25).
Kindly inform widely the customers relations about this as, we are receiving lot of
these requests on our side.

@Vanessa, kindly monitor the traffic of all these numbers, and close the ticket
accordingly.

***********************************************************************************
*****