MC55_ATC_V04.00 Page 80 of 475 3/17/06
Confidential / Released
3.4.11 SIEMENS release cause for Session Management (SM)3.4.12 GSM cause for L3 Protocol module or other local cause 3.4.13 SIEMENS release cause for GPRS API3.4.14 SIEMENS release cause for PPP/IP-StackNumber Description
3 The MS has not got any answer to the ACTIVATE PDP CONTEXT request message sent five
times to the network
4 A MT PDP context which is active or in the activation process is deactivated because another
MT PDP context with the same TI is requested by the network to be activated
5 A MT PDP context which is active or in the activation process is deactivated because another
MT PDP context with the same TI is requested by the network to be activated. The activation
request is rejected by the SM sending the cause 'insufficient resources' to the network
because the SM was not able to perform the necessary comparisons for a static PDP address
collision detection.
6 A MT PDP context which is active or in the activation process is deactivated because another
MT PDP context with the same TI is requested by the network to be activated. As a static PDP
address collision with an MO activating PDP context has been detected by the SM the SM dis-
cards the activation request
7 A MT PDP context request has been indicated but could not be processed in time. The acti-
vation request is rejected by the SM sending the cause 'insufficient resources' to the network.
Number Description
2 No detailed cause
Number Description
0 Regular deactivation of the call
1 Action temporarily not allowed
2 Wrong connection type
3 Specified data service profile invalid
4 PDP type or address is unknown
5 FDN Check was not successful; GPRS Attach and PDP Context Activation blocked
255 Undefined
Number Description
0 Regular call deactivation
1 LCP stopped
255 Undefined