Cisco Cisco Packet Data Gateway (PDG)
• 26 - Failure in the Radio Interface Procedure
• 27 - Invalid QoS combination
• 28 - Inter-RAT redirection
• 29 - Interaction with other procedure
• 30 - Unknown E-RAB ID
• 31 - Multiple E-RAB ID instances
• 32 - Encryption and/or integrity protection algorithms not supported
• 33 - S1 intra-system Handover triggered
• 34 - S1 inter system Handover triggered
• 35 - X2 Handover triggered ...
• 36 - Redirection towards 1xRTT
• 37 - Not supported QCI value
• 38 - invalid CSG Id
s1-nas-cause cause_value
Specifies the S1 NAS cause code that needs to be mapped.
tau-reject
Specifies the TAU reject message sent by MME.
Usage Guidelines
By default, an MME initiates the UE-CONTEXT-RELEASE with cause NAS-Normal-Release whenever the
MME receives any procedure Request over Initial-UE if the UE is in the connected state. This command
makes it possible for the operator to configure a preferred cause code for the reason of the disconnect.
MME receives any procedure Request over Initial-UE if the UE is in the connected state. This command
makes it possible for the operator to configure a preferred cause code for the reason of the disconnect.
In earlier releases, the keyword was init-ue-from-enodeb-for-tau. In release 19.2, the name and behavior
associated with this keyword changed. The keyword name is init-ue-from-enodeb. In support of backward
compatibility, the MME will accept configurations with either form of the keyword. When the operator
explicitly saves the configuration, the configuration will save using the new form of the keyword.
associated with this keyword changed. The keyword name is init-ue-from-enodeb. In support of backward
compatibility, the MME will accept configurations with either form of the keyword. When the operator
explicitly saves the configuration, the configuration will save using the new form of the keyword.
Important
Beginning with release 19.2, the init-ue-from-enodeb reason instructs the MME to initiate the
UE-CONTEXT-RELEASE with cause NAS-Normal-Release whenever the MME receives a request over
Initial-UE not just for TAU but for all TAU and non-TAU scenarios (such as Service Request, Attach, and
Extended-Service-Request) if the UE is in the connected state.
UE-CONTEXT-RELEASE with cause NAS-Normal-Release whenever the MME receives a request over
Initial-UE not just for TAU but for all TAU and non-TAU scenarios (such as Service Request, Attach, and
Extended-Service-Request) if the UE is in the connected state.
In release 19.5, MME is modified to include S1 NAS Cause Code mapping. This configuration allows the
MME to configure the S1 NAS cause code mapping to be sent in S1-UE-CONTEXT-RELEASE initiated
from the MME after an ATTACH or TAU is rejected with a specific EMM cause code or any EMM cause
code. The newly configured S1 NAS cause code is sent in the UE-CONTEXT-RELEASE message whenever
MME releases the existing S1AP connection with the configured S1 NAS cause after an ATTACH/TAU
message gets rejected, along with a specific EMM cause or any EMM cause code based on the configuration.
MME to configure the S1 NAS cause code mapping to be sent in S1-UE-CONTEXT-RELEASE initiated
from the MME after an ATTACH or TAU is rejected with a specific EMM cause code or any EMM cause
code. The newly configured S1 NAS cause code is sent in the UE-CONTEXT-RELEASE message whenever
MME releases the existing S1AP connection with the configured S1 NAS cause after an ATTACH/TAU
message gets rejected, along with a specific EMM cause or any EMM cause code based on the configuration.
Command Line Interface Reference, Modes I - Q, StarOS Release 19
995
MME Service Configuration Mode Commands
s1-ue-context-release