> 11.2 | AT+CGANS Manual response to a network request for PDP context activation

> Syntax

> Test Command AT+CGANS=?
> Response(s)
> +CGANS: (list of supported <response>s), (list of supported <L2P>s)
> OK

> Write Command AT+CGANS=[<response>[, <L2P>[, <cid>]]]
> Response(s)
> CONNECT
> NO CARRIER
> ERROR
> +CME ERROR

> Reference(s) |  | PIN |  | ASC0 | ASC1 | USB | MUX1 | MUX2 | MUX3 |  |  | Charge | Q | Last
> GSM 07.07 |  | + |  | + | + | + | + | + | + |  |  | - | - | +

> Command Description
> The write command requests the MT to respond to a network request for GPRS PDP context activation which has been signaled to the TE by the RING or CRING unsolicited result code. The <response> parameter allows the TE to accept or reject the request.
> Parameter Description

> <response>(num)

> [0]
> the request is rejected and the MT returns OK to the TE
> 1
> accept and request that the PDP context be activated

> <L2P>(str)

> a string parameter which indicates the layer 2 protocol to be used (see AT+CGDATA command)

> <cid>(num)

> a numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command).
> Note

> • | If <response> is 1, the following procedure is followed by the MT: If the <L2P> parameter value is unacceptable to the MT, the MT will return an ERROR or +CME ERROR response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. A <cid> may be specified for use in the context activation request. During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP context activation message. If this is in conflict with the information provided by a specified <cid>, the command will fail. There will be no conflict, if the PDP type matches exactly and the PDP address given by the context definition for <cid> is empty or matches exactly with the address specified with the network PDP context activation message. The context will be activated using the values for PDP type and address provided by the network, together with all other information found in the PDP context definition. An APN may or may not be required, depending on the application. If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and address provided by the network. The other parameters will be set to their default values (see AT+CGDCONT). If activation is successful, data transfer may proceed. After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is reentered and the MT returns the final result code OK. In the event of an erroneous termination or a failure to start up, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER, or if enabled, +CME ERROR. Attach, activate and other errors may be reported. It is also an error to issue the AT+CGANS command when there is no pending network request. The command may be used in both normal and modem compatibility modes.