Cisco Cisco ASR 5000
Network Requested Secondary PDP Context Activation
How It Works ▀
SGSN Administration Guide, StarOS Release 18 ▄
Table 23.
SM-to-GTP Cause Mapping
SM Cause
GTP Cause
#26, Insufficient resources
#199, No resources available
#31, activation rejected, unspecified
#197, MS refuses
#40, feature not supported
#200, Service not supported
#41, semantic error in TFT operation
#215, semantic error in TFT operation
#42, syntactical error in TFT operation
#216, syntactical error in TFT operation
#43, unknown PDP context
#210, Context not found
#44, semantic error in packet filter(s)
#217, semantic error in packet filter(s)
#45, syntactical error in packet filter(s)
#218, syntactical error in packet filter(s)
#46, PDP context without TFT already activated
#221, PDP context without TFT already activated
#48, activation rejected, BCM violation
#227, BCM violation
#95 - protocol error
#197, MS refuses
Upon receipt of an Activate Secondary PDP Context Request or Requested Secondary PDP Context Activation Reject
message, the SGSN stops the T3385 timer.
message, the SGSN stops the T3385 timer.
Figure 65. Call Flow: Unsuccessful Network Requested Secondary Activation (Gn/Gp)
The SGSN will reject the IPCA for the following conditions:
Subscriber has switched to CS call with cause “GPRS connection suspended”.
Old SGSN RAU/SRNS is ongoing with cause “MS is not GPRS responding”.
IPCA Request is received when BCM is MS only with “BCM mode violation”.