Mobility Management Cause Codes

Table 1 Mobility Management Cause Codes

Decimal number 2

Name

Description

Action Only SGSN (G):

IMSI unknown in HLR Only SGSN (G):

Illegal MS

The MSV/VLR rejects a Check the CS Combined PS/CS subscription. Attach procedure. The MSC/VLR rejects due to non CS subscription. Only SGSN (G): Only SGSN (G): Check why MSC/VLR treats the MS as "illegal".

Occurs when the MS requests a Combined CS/PS Attach or RA Update and the location updating towards MSC/VLR is rejected. Illegal ME Check IMEI towards EIR results in a blacklisted Mobile Equipment (ME). General Packet Radio There is no GPRS Service (GPRS) subscription in the services not allowed Home Location Register (HLR) for this particular IMSI. GPRS services and The IMSI is unknown non-GPRS services not in the HLR. allowed

Check with operator why the ME is blacklisted. Check the configuration in the HLR.

Check the configuration in the HLR. Also, check the IMSI number series and Global Title (GT) rule configuration in the SGSN. MS identity cannot be The SGSN verifies that Check if the RAI of old derived by the the old RAI is not SGSN will be network defined as configured as Cooperating Routing Cooperating RA. Area (RA). SGSN cannot derive the MS's identity from the PTMSI in case of interSGSN RA update.

10

Impliticly detached

The MS must reattach None and usually takes place when: An unattached MS sends a RAU request to the SGSN. An UL payload is received for an unattached MS.

11

PLMN not allowed

12

Location area not allowed

The SGSN is Check the Roaming configured with Restrictions Roaming Restrictions. configuration in the SGSN, if this IMSI should be able to roam in this location area. Only SGSN (W): Only SGSN (W): The MS requests a Combined CS/PS RA Update and the location updating towards MSC/VLR is rejected with in a location area where the MS, by subscription, is not allowed to operate. The SGSN is configured with Roaming Restrictions. Check if the MS is allowed to operate CS services in that location area.

13

Roaming not allowed in this Location Area

14

GPRS services not allowed in this PLMN

There is no IMSI series configured in the SGSN that matches this subscriber's IMSI. The HLR returns Check the "Roaming not allowed" configuration in the HLR. in Update GPRS Location Response.

Check the Roaming Restrictions configuration in the SGSN, if this IMSI should be able to roam in this location area. Check the IMSI series configuration in the SGSN.

The MS has indicated that ciphering is not supported, but the Gb_UncipheredMode node property does not allow an unciphered connection. The SGSN is configured with Roaming Restrictions.

Change the Gb_UncipheredMode node property, if unciphered connections shall be allowed.

15

No suitable cells in location area

16

MSC temporarily not reachable

Check the Roaming Restrictions configuration in the SGSN, if this IMSI should be able to roam in this location area. The SGSN is Check the Roaming configured with Restrictions Roaming Restrictions. configuration in the SGSN, if this IMSI should be able to roam in this location area. The MS is not allowed Check the to attach in the configuration of the current Location Area LA/Routing Area (RA). (LA). See the Iu-C interface troubleshooting in Section 8.4. Only SGSN (G): Only SGSN (G): The MS requests a Combined CS/PS RA Update and the location updating towards MSC/VLR is rejected. The HLR does not respond to the SGSN messages, or the SGSN cannot send messages to the HLR. Check if MSC/VLR is down.

17

Network failure

Check the Gr interface. Also, check the IMSI number series, GT rule, and SS7 routing configuration. This occurs when the Check the HLR during configuration in the authentication sends HLR. an empty response to See the mobility event the SGSN. logs for more information on this cause code.

22

Congestion

95

96 97

(1)

99

100 111

Investigate traffic load and check if Central Processing Unit (CPU)demanding features are turned on. The attach limit of the Check attach limit and SGSN has been compare with the reached. The attach number of attached limit is the maximum subscribers. allowed Simultaneously Attached Users (SAU), which is a parameter that is connected to product licensing. Semantically incorrect The SGSN regards the Use a protocol message Attach Request analyzer to look for message as incorrect. protocol errors in the message sent by the MS. Invalid mandatory See cause code 95. See cause code 95. information Message type nonSee cause code 95. See cause code 95. existent or not implemented Information element See cause code 95. See cause code 95. non-existent or not implemented Conditional IE error See cause code 95. See cause code 95. Only SGSN (W): Only SGSN (W): Protocol error, unspecified This occurs when the Check the Iu-C Radio Network interface, see Section 8.4. Controller (RNC) sends "Security Mode Reject" to the SGSN Check the RNC as an answer from configuration in the "Security Mode SGSN. Command". See cause code 95. See cause code 95.

The processing load on the SGSN is too high.

(1) Using the optionally supported Multi-Operator Core Network (MOCN) feature, the number of rejects with this cause code is normally high, due to coordination of the CS and PS domains.

Session Management Cause Codes

Table 2 Session Management Cause Codes

Decimal number 25

Name

Description

Action Use a protocol analyzer to look for protocol errors in the message sent by the MS.

26

LLC or SNDCP failure Indicates that a PDP context is deactivated because of a LLC or SNDCP failure. For example if the SM receives a SNSM-STATUS request message with cause "DM received " or "invalid XID response". Insufficient All dynamic IP addresses resources in GGSN are occupied. Only SGSN (W):

Check the GGSN status. Only SGSN (W):

27

28

RAB Assignment is Check the RNC status. rejected by the RNC. Missing or unknown The APN is not included in Check the APN the DNS. configuration in the DNS. No response from the Check the DNS. configuration in the SGSN and the configuration of the interface on which DNS is used. See the session event logs for information about this cause code. Unknown PDP Indicates that the See the session event address or PDP type requested service was logs for information rejected by the external about this cause code. Packet Data Network (PDN), because the PDP address or type could not be recognized.

29

User authentication failed

Indicates that the requested service was rejected by the external PDN due to a failed user authentication.

Check that the MS sends valid Protocol Configuration Options in the Activate PDP Context Request message.

30

Activation rejected by GGSN

31

Activation rejected, unspecified Service option not supported

32

33

Requested service option not subscribed

Check the configuration of RADIUS/Dynamic Host Configuration Protocol (DHCP) servers in the external PDN. Setting up a secondary Secondary PDP PDP context when the context is not primary context is set up supported if GTPv0 is using GTPv0. used. Most probable reason, the Troubleshoot the attach procedure was attach sequence. unsuccessful. Most probable reason, Check the PDP type in Active PDP Context the Activate PDP Request requests a non- Context Request supported PDP type. message. Activation denied since Check subscriber data the requested values sent in the HLR and in Active PDP Context requested values sent Request does not match in Active PDP Context values stored in the HLR. Request Example: A MS requests a static IP address but the subscription is for dynamic. If Misconfigured MT If Misconfigured MT Identification is Identification is activated: activated:

36

Check the session event log to identify the MSs using incorrect information when requesting a PDP context activation. Regular PDP context Indicates a regular MS- or No action. deactivation network- initiated PDP context deactivation.

The MS is logged in the session event log.

38

Network failure

No Create PDP Context Check the status of Response is received from the GGSN and the Gn the GGSN. interface. Only SGSN (W): Only SGSN (W): No RAB Assignment Response is received within the TRABAssgt timeout. Check the status of the RNC. If RAB Assignment is sent from the RNC, check or increase the node property Iu_TRABassgt. See the session event logs for information about this cause code. The GGSN regards the Use a protocol TFT and IP Packet Filters analyzer to look for as incorrect. protocol errors in the message sent by the MS and the SGSN to the GGSN. The primary PDP context Troubleshoot the is not active when trying activation of the to activate a secondary primary PDP context. PDP context. The SGSN regards the Use a protocol Attach Request message analyzer to look for as incorrect. protocol errors in the message sent by the MS. See cause code 95. See cause code 95. See cause code 95. See cause code 95.

41, 42, 44, 45, 46

TFT and IP Packet Filter errors

43

Unknown PDP context

95

Semantically incorrect message

96 97

99

100 111

Invalid mandatory information Message type nonexistent or not implemented Information element non-existent or not implemented Conditional IE error Protocol error, unspecified

See cause code 95.

See cause code 95.

See cause code 95. Only SGSN (W): This occurs when the RNC sends a Security Mode Reject message to the SGSN as an answer from Security Mode Command. See cause code 95.

See cause code 95. Only SGSN (W): Check the Iu interface. Check the RNC configuration. See cause code 95.