BGS2T AT Command Set
3.4 AT+CEER
BGS2T_ATC_V01.301
Page 88 of 554
1/31/12
c
3.4.16
GSM cause for L3 Protocol module or other local cause
3.4.17
Proprietary release cause for GPRS API
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. 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.
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 beactivated. 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
6
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.
7
GAPI rejected a PDP context activation request or rejected of a activation request for a sec-
ondary PDP context.
8
As the consequence of a handover from a release 1999 to a GPRS release 1997/98 network
all PDP contexts with the same PDP address and APN are deactivated except the one with
the highest QoS.
9
deactivation of a PDP context initiated by the RABM.
10
The GAPI has requested either a secondary PDP context activation or a MS initiated PDP con-
text modification in a release 1997/98 network. As these features both are not supported by in
Release 1997/98, the SM rejects the request.
11
rejection of a PDP context modification request because of missing a new QoS or a new TFT.
12
The network requests to activate a PDP context with the same combination of APN and PDP
address as an already activated PDP context. The MS has to deactivate the already activated
PDP context and all linked PDP contexts (matching the combination of APN and PDP
address) locally.
13
The network indicates that a PDP context which is regarded as not inactive by the MS is
regarded as inactive by the network. The MS has to deactivate this PDP context locally.
Number
Description
2
no detailed cause
Number
Description
0
regular deactivation of the call
1
action temporary 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
9
GPRS service not available
255
undefined
Number
Description
Confidential / Released