# Quectel Modules with Super SIM

## Cellular modems covered on this page <a href="#cellular-modems-covered-on-this-page" id="cellular-modems-covered-on-this-page"></a>

* [BG95/BG96](#bg95bg96-cat-m1-nb-iot-gsm)
* [EG21-G](#eg21-g-cat-1-gsm)
* [EG25-G](#eg25-g-cat-4-gsm)

***

## Firmware updates <a href="#firmware-updates" id="firmware-updates"></a>

Firmware updates for Quectel cellular modules are typically available through Quectel support. Please reach out to your Quectel representative or [Quectel Support](https://www.quectel.com/support/contact.htm) for assistance with firmware updates.

***

## General getting started information <a href="#general-getting-started-information" id="general-getting-started-information"></a>

Please refer to the main Knowlegdebase page for [modem-independent configuration tips](https://docs.korewireless.com/en-us/supersim/cellular-module-knowledgebase/overview).

***

## BG95/BG96 `Cat-M1, NB-IoT, GSM` <a href="#bg95bg96-cat-m1-nb-iot-gsm" id="bg95bg96-cat-m1-nb-iot-gsm"></a>

{% hint style="danger" %}
Super SIM does not support NB-IoT.
{% endhint %}

### Initialization <a href="#initialization" id="initialization"></a>

If you are connecting via LTE, only configure the modem's Radio Access Technology (RAT) preference to Cat-M1: issue the Quectel-specific command `AT+QCFG="iotopmode"` with its default setting, `0`, the first numeric parameter of the command below.

```
AT+QCFG="iotopmode",0,1
```

{% hint style="danger" %}
If `iotopmode` is set to `1` (NB-IoT), the modem will **not** be able to connect to Cat-M1.
{% endhint %}

If you wish to limit comms to LTE only, i.e., disable 2G (GSM), issue:

```bash
AT+QCFG="nwscanmode",3,1
```

The first numeric parameter, `3`, indicates LTE only; a value of `1` sets the modem to GSM only. The default, `0`, tells the modem to select the RAT automatically. The setting is applied immediately.

### Data-centric attach mode <a href="#data-centric-attach-mode" id="data-centric-attach-mode"></a>

To set the modem to force data-centric attachment — ie., do not make circuit-switched attachments — issue `AT+QCFG="servicedomain",1,1`.

The first numeric parameter is the mode:

* `1` = Packet Switch (PS) attach only.
* `2` = Circuit Switch and Packet Switch (CS/PS) attach.

This setting is non-volatile.

### Configure the URC UART <a href="#configure-the-urc-uart" id="configure-the-urc-uart"></a>

To configure the Unsolicited Result Code (URC) serial (UART) delivery channel to `uart1`, issue `AT+QURCCFG="urcport","uart1"`.

### Perform a ping <a href="#perform-a-ping" id="perform-a-ping"></a>

To perform a ping to a remote host, issue `AT+QPING=1,"<TARGET_IP_ADDRESS_OR_NAME>"`. This will yield, for example:

```bash
+QPING: 0,"8.8.8.8",32,93,255
+QPING: 0,"8.8.8.8",32,78,255
+QPING: 0,"8.8.8.8",32,80,255
+QPING: 0,"8.8.8.8",32,80,255
+QPING: 0,4,4,0,78,93,82
```

### Perform an HTTP GET <a href="#perform-an-http-get" id="perform-an-http-get"></a>

To issue an HTTP `GET` request using the built-in HTTP client, run the following commands:

1. Set the PDP context ID: `AT+QHTTPCFG="contextid",1`
2. Enable output of HTTP response headers: `AT+QHTTPCFG="responseheader",1`
3. Activate the PDP context: `AT+QIACT=1`
4. Set the target URL: `AT+QHTTPURL=21`This sets the modem to receive, prompted by the output `CONNECT`. The first parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of `21` comes from the URL below. The URL you provide must include the protocol, ie. `http://`.
5. Upon `CONNECT`, enter the URL. For example: `http://ifconfig.co/ip`
6. Issue a `GET` request: `AT+QHTTPGET`
7. View the request: `AT+QHTTPREAD`

The request will look like this:

```html
HTTP/1.1 200 OK
Date: Sat, 28 Nov 2020 18:38:52 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 15
Connection: keep-alive
Set-Cookie: __cfduid=d33c30006be23245591d83133631425031606588732; expires=Mon, 28-Dec-20 18:38:52 GMT; path=/; domain=.ifconfig.co; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=15768000; includeSubdomains; preload
CF-Cache-Status: DYNAMIC
cf-request-id: 06b1bfaa91000025ed8fa46000000001
0Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=8eYWG5vobibOeI8xWFxNSGJpELSCSthW9aAclBXw3esKOGBsYPT4izdckGI2kpOW%2BA7KOhi3OFk%2FLUab3RpQvKu5EYYWLD%2B2fSxV4Q%3D%3D"}],"group":"cf-nel","max_age":604800}
1NEL: {"report_to":"cf-nel","max_age":604800}
2Server: cloudflare
3CF-RAY: 5f96355748c225ed-IAD
4
599.84.181.20
6
7OK
8+QHTTPREAD: 0
```

{% hint style="danger" %}
This example uses a service that returns the IP address of the requester.
{% endhint %}

{% hint style="info" %}
If you need to provide extra HTTP request headers, such `Authorization: Basic <API_KEY>`, or a custom header required by your server, issue `AT+QHTTPCFG="requestheader",1` to tell the modem to use the custom header that you will provide when you make each request. You must create a full HTTP request header separated from your request body by `<CR><LF>` characters. Whether you make a `POST` or a `GET` request, include a byte-count parameter that totals the header plus the body (`POST` request) or header alone (`GET` request). For example, `AT+QHTTPGET=60,512` for a 512-byte header (including the end-of-header `<CR><LF>`). The `60` is a timeout. This defaults to 60 seconds but must be included if a second parameter is also present.
{% endhint %}

{% hint style="info" %}
You can check the status of a PDP context with `AT+QIACT?`. If activated, this will return the context ID; `0` or `1` whether the context is inactive or active; `1` or `2` whether the context is using IPv4 or IPv6; and the device's IP address.
{% endhint %}

### Perform an HTTPS GET <a href="#perform-an-https-get" id="perform-an-https-get"></a>

To issue an HTTPS `GET` request using the built-in HTTP client, follow the same procedure outlined above but with extra steps to configure SSL.

1. Set the PDP context ID: `AT+QHTTPCFG="contextid",1`
2. Enable output of HTTP response headers: `AT+QHTTPCFG="responseheader",1`
3. Activate the PDP context if it is not already active: `AT+QIACT=1`
4. Select the SSL context ID for this PDP context ID: `AT+QHTTPCFG="sslctxid",1`
5. Set the SSL version. Choose TLS 1.2: `AT+QSSLCFG="sslversion",1,3`
6. Set the SSL cipher suite. Choose all types: `AT+QSSLCFG="ciphersuite",1,0xFFFF`
7. For testing, set the SSL verification level to `0`, i.e., no CA certificate is required: `AT+QSSLCFG="seclevel"=0`
8. Set the target URL: `AT+QHTTPURL=70`This sets the modem to receive, prompted by the output `CONNECT`. The parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of `70` comes from the URL below. The URL you provide must include the protocol, ie. `https://`.
9. Upon receiving `CONNECT`, enter the URL. For example: `https://twilio-cms-prod.s3.amazonaws.com/documents/super-sim-test.json`
10. Issue a `GET` request: `AT+QHTTPGET`
11. View the response: `AT+QHTTPREAD`

The request will look something like this:

```html
HTTP/1.1 200 OK
Date: Thu, 19 May 2022 10:23:25 GMT
Last-Modified: Thu, 19 May 2022 10:05:25 GMT
Accept-Ranges: bytes
Content-Type: application/json
Server: AmazonS3
Content-Length: 128

{
   "userId": 1,
   "id": 5,
   "title": "laboriosam mollitia et enim quasi adipisci quia provident illum",
   "completed": false,
}                                                                                                                         }
OK

+QHTTPREAD: 0
```

### Perform an HTTP(S) POST <a href="#perform-an-https-post" id="perform-an-https-post"></a>

Sending data from the modem to an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols: call `AT+QHTTPOST` instead of `AT+QHTTPGET`.

Optionally, the `QHTTPOST` command takes a parameter indicating the amount of data you are sending. The modem uses this to read that number of bytes via the UART over which your application is communicating with it. If you are providing a custom HTTP request header, remember to include its length too.

### Low-power modes <a href="#low-power-modes" id="low-power-modes"></a>

While the BG95 and 96 support low-power modes for eDRX and PSM, support for these features will vary by visited network and location. The commands to enable for each of these are:

```bash
AT+CEDRXS=1
AT+CPSMS=1
```

*See also `AT+QPTWEDRXS` and `AT+CEDRXRDP` in the BG95/96 AT Commands Manual for further options.*

Using these features, but especially PSM, can make the modem inaccessible to the terminal during its sleep time. It's best to experiment with these features locally. To disable all power saving, send:

<pre class="language-bash"><code class="lang-bash">AT+CEDRXS=0
<strong>AT+CPSMS=0
</strong></code></pre>

You can learn more about implementing these modes in our [low-power usage documentation](https://docs.korewireless.com/en-us/supersim/cellular-module-knowledgebase/low-power-optimization-for-cellular-modules).

### Known issues <a href="#known-issues" id="known-issues"></a>

The BG95 and BG96 will connect to 2G if they are unable to connect to Cat-M1 and 2G has not been disabled. Unfortunately, if Cat-M1 coverage is restored, or the device moves into an area where Cat-M1 is available, the modem will nonetheless continue to connect to 2G. This is because Quectel modems favor the most recently used RAT when they reconnect, and this value is persisted in non-volatile memory.

To avoid this issue, you can use the following AT command in your application to clear the stored RAT by resetting the modem's RAT searching sequence:

```bash
AT+QCFG="nwscanseq",020103,1
```

The parameter `020103` represents the RAT sequence: `02` is Cat-M1, `01` is GSM, and `03` is NB-IoT. Super SIM is not compatible with NB-IoT, so this is placed last.

The final `1` forces the sequence to be applied immediately, avoiding the need to reboot the modem. Leave this parameter off, or set it to `0`, to impose the new sequence on the next power cycle.

### Additional resources <a href="#additional-resources" id="additional-resources"></a>

• [BG96 AT Commands Manual](https://www.quectel.com/download/quectel_bg96_at_commands_manual_v2-3) *Quectel sign-in required* • [BG95, BG77, and BG600L Series AT Commands Manual](https://www.quectel.com/download/quectel_bg95bg77bg600l_series_at_commands_manual_v2-0) *Quectel sign-in required*

***

## EG21-G `Cat-1, GSM` <a href="#eg21-g-cat-1-gsm" id="eg21-g-cat-1-gsm"></a>

### Initialization <a href="#initialization-2" id="initialization-2"></a>

If you wish to limit communications to LTE only, i.e., to disable 2G (GSM), issue this command:

```bash
AT+QCFG="nwscanmode",3
```

This setting will be applied immediately.

### Data-centric attach mode <a href="#data-centric-attach-mode-2" id="data-centric-attach-mode-2"></a>

To instruct the modem to initiate data-centric attachments only — ie., not to make voice-oriented circuit-switched attachments too, which is the default — issue:

```bash
AT+QCFG="servicedomain",1
```

This setting will be applied immediately.

### Configure the URC UART <a href="#configure-the-urc-uart-2" id="configure-the-urc-uart-2"></a>

To configure the Unsolicited Result Code (URC) serial (UART) delivery channel to `uart1`, issue `AT+QURCCFG="urcport","uart1"`.

### Perform a ping <a href="#perform-a-ping-2" id="perform-a-ping-2"></a>

To perform a ping to a remote host, issue `AT+QPING=1,"<TARGET_IP_ADDRESS_OR_NAME>"`. This will yield, for example:

```bash
+QPING: 0,"8.8.8.8",32,172,255
+QPING: 0,"8.8.8.8",32,212,255
+QPING: 0,"8.8.8.8",32,376,255
+QPING: 0,"8.8.8.8",32,174,255
+QPING: 0,4,4,0,172,376,233
```

### Perform an HTTP GET <a href="#perform-an-http-get-2" id="perform-an-http-get-2"></a>

To issue an HTTP `GET` request using the built-in HTTP client, run the following commands:

1. Set the PDP context ID: `AT+QHTTPCFG="contextid",1`
2. Enable output of HTTP response headers: `AT+QHTTPCFG="responseheader",1`
3. Activate the PDP context: `AT+QIACT=1`
4. Set the target URL: `AT+QHTTPURL=21`This sets the modem to receive, prompted by the output `CONNECT`. The first parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The URL you provide must include the protocol, ie. `http://`.
5. Upon `CONNECT`, enter the URL. For example: `http://ifconfig.co/ip`
6. Issue a `GET` request: `AT+QHTTPGET`
7. View the request: `AT+QHTTPREAD`

The request will look like this:

```html
HTTP/1.1 200 OK
Date: Sat, 28 Nov 2020 18:38:52 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 15
Connection: keep-alive
Set-Cookie: __cfduid=d33c30006be23245591d83133631425031606588732; expires=Mon, 28-Dec-20 18:38:52 GMT; path=/; domain=.ifconfig.co; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=15768000; includeSubdomains; preload
CF-Cache-Status: DYNAMIC
cf-request-id: 06b1bfaa91000025ed8fa46000000001
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=8eYWG5vobibOeI8xWFxNSGJpELSCSthW9aAclBXw3esKOGBsYPT4izdckGI2kpOW%2BA7KOhi3OFk%2FLUab3RpQvKu5EYYWLD%2B2fSxV4Q%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 5f96355748c225ed-IAD

99.84.181.20

OK
+QHTTPREAD: 0
```

{% hint style="danger" %}
This example uses a service that returns the IP address of the requester.
{% endhint %}

{% hint style="info" %}
If you need to provide extra HTTP request headers, such `Authorization: Basic <API_KEY>`, or a custom header required by your server, issue `AT+QHTTPCFG="requestheader",1` to tell the modem to use the custom header that you will provide when you make each request. You must create a full HTTP request header separated from your request body by `<CR><LF>` characters. Whether you make a `POST` or a `GET` request, include a byte-count parameter that totals the header plus the body (`POST` request) or header alone (`GET` request). For example, `AT+QHTTPGET=60,512` for a 512-byte header (including the end-of-header `<CR><LF>`). The `60` is a timeout. This defaults to 60 seconds but must be included if a second parameter is also present.
{% endhint %}

{% hint style="info" %}
You can check the status of a PDP context with `AT+QIACT?`. If activated, this will return the context ID; `0` or `1` whether the context is inactive or active; `1` or `2` whether the context is using IPv4 or IPv6; and the device's IP address.
{% endhint %}

### Perform an HTTPS GET <a href="#perform-an-https-get-2" id="perform-an-https-get-2"></a>

To issue an HTTPS `GET` request using the built-in HTTP client, follow the same procedure outlined above but with extra steps to configure SSL.

1. Set the PDP context ID: `AT+QHTTPCFG="contextid",1`
2. Enable output of HTTP response headers: `AT+QHTTPCFG="responseheader",1`
3. Activate the PDP context if it is not already active: `AT+QIACT=1`
4. Select the SSL context ID for this PDP context ID: `AT+QHTTPCFG="sslctxid",1`
5. Set the SSL version. Choose TLS 1.2: `AT+QSSLCFG="sslversion",1,3`
6. Set the SSL cipher suite. Choose all types: `AT+QSSLCFG="ciphersuite",1,0xFFFF`
7. For testing, set the SSL verification level to `0`, i.e., no CA certificate is required: `AT+QSSLCFG="seclevel"=0`
8. Set the target URL: `AT+QHTTPURL=70`This sets the modem to receive, prompted by the output `CONNECT`. The parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of `70` comes from the URL below. The URL you provide must include the protocol, ie. `https://`.
9. Upon receiving `CONNECT`, enter the URL. For example: <https://twilio-cms-prod.s3.amazonaws.com/documents/super-sim-test.json>
10. Issue a `GET` request: `AT+QHTTPGET`
11. View the response: `AT+QHTTPREAD`

The request will look something like this:

```html
HTTP/1.1 200 OK
Date: Thu, 19 May 2022 10:23:25 GMT
Last-Modified: Thu, 19 May 2022 10:05:25 GMT
Accept-Ranges: bytes
Content-Type: application/json
Server: AmazonS3
Content-Length: 128

{
   "userId": 1,
   "id": 5,
   "title": "laboriosam mollitia et enim quasi adipisci quia provident illum",
   "completed": false,
}                                                                                                                         }
OK
+QHTTPREAD: 0
```

### Perform an HTTP(S) POST <a href="#perform-an-http-s--post-2" id="perform-an-http-s--post-2"></a>

Sending data from the modem to an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols: call `AT+QHTTPOST` instead of `AT+QHTTPGET`.

Optionally, the `QHTTPOST` command takes a parameter indicating the amount of data you are sending. The modem uses this to read that number of bytes via the UART over which your application is communicating with it. If you are providing a custom HTTP request header, remember to include its length too.

### Low-power modes <a href="#low-power-modes-2" id="low-power-modes-2"></a>

The EG21-G does not support eDRX and PSM.

### Additional resources <a href="#additional-resources-2" id="additional-resources-2"></a>

• [EG21-G AT Commands Manual](https://www.quectel.com/download_file/2027) *Quectel sign-in required*

***

## EG25-G `Cat-4, GSM` <a href="#eg25-g-cat-4-gsm" id="eg25-g-cat-4-gsm"></a>

### Initialization <a href="#initialization-3" id="initialization-3"></a>

If you wish to limit communications to LTE only, i.e., to disable 2G (GSM), issue this command:

```bash
AT+QCFG="nwscanmode",3
```

This setting will be applied immediately.

### Data-centric attach mode <a href="#data-centric-attach-mode-3" id="data-centric-attach-mode-3"></a>

To instruct the modem to initiate data-centric attachments only — ie., not to make voice-oriented circuit-switched attachments too, which is the default — issue:

```bash
AT+QCFG="servicedomain",1
```

This setting will be applied immediately.

### Configure the URC UART <a href="#configure-the-urc-uart-3" id="configure-the-urc-uart-3"></a>

To configure the Unsolicited Result Code (URC) serial (UART) delivery channel to `uart1`, issue `AT+QURCCFG="urcport","uart1"`.

### Perform a ping <a href="#perform-a-ping-3" id="perform-a-ping-3"></a>

To perform a ping to a remote host, issue `AT+QPING=1,"<TARGET_IP_ADDRESS_OR_NAME>"`. This will yield, for example:

```bash
+QPING: 0,"8.8.8.8",32,167,255
+QPING: 0,"8.8.8.8",32,162,255
+QPING: 0,"8.8.8.8",32,164,255
+QPING: 0,"8.8.8.8",32,162,255
+QPING: 0,4,4,0,162,167,163
```

### Perform an HTTP GET <a href="#perform-an-http-get-3" id="perform-an-http-get-3"></a>

To issue an HTTP `GET` request using the built-in HTTP client, run the following commands:

1. Set the PDP context ID: `AT+QHTTPCFG="contextid",1`
2. Enable output of HTTP response headers: `AT+QHTTPCFG="responseheader",1`
3. Activate the PDP context: `AT+QIACT=1`
4. Set the target URL: `AT+QHTTPURL=21`This sets the modem to receive, prompted by the output `CONNECT`. The first parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The URL you provide must include the protocol, ie. `http://`.
5. Upon `CONNECT`, enter the URL. For example: `http://ifconfig.co/ip`
6. Issue a `GET` request: `AT+QHTTPGET`
7. View the request: `AT+QHTTPREAD`

The request will look like this:

```html
HTTP/1.1 200 OK
Date: Fri, 20 May 2022 08:52:56 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 13
Connection: keep-alive
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=9fl%2B3t%2FRMhY2tMyWQDFAIM1mfFem0zLc7aONeXJ%2Fg4a%2FJPKFl%2BeGYElL5zwwuxi7%2BIfqx}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 70e3d6ceb8cc5b17-IAD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

44.204.32.40

OK

+QHTTPREAD: 0
```

{% hint style="info" %}
This example uses a service that returns the IP address of the requester.
{% endhint %}

{% hint style="info" %}
If you need to provide extra HTTP request headers, such `Authorization: Basic <API_KEY>`, or a custom header required by your server, issue `AT+QHTTPCFG="requestheader",1` to tell the modem to use the custom header that you will provide when you make each request. You must create a full HTTP request header separated from your request body by `<CR><LF>` characters. Whether you make a `POST` or a `GET` request, include a byte-count parameter that totals the header plus the body (`POST` request) or header alone (`GET` request). For example, `AT+QHTTPGET=60,512` for a 512-byte header (including the end-of-header `<CR><LF>`). The `60` is a timeout. This defaults to 60 seconds but must be included if a second parameter is also present.
{% endhint %}

{% hint style="info" %}
You can check the status of a PDP context with `AT+QIACT?`. If activated, this will return the context ID; `0` or `1` whether the context is inactive or active; `1` or `2` whether the context is using IPv4 or IPv6; and the device's IP address.
{% endhint %}

### Perform an HTTPS GET <a href="#perform-an-https-get-3" id="perform-an-https-get-3"></a>

To issue an HTTPS `GET` request using the built-in HTTP client, follow the same procedure outlined above but with extra steps to configure SSL.

1. Set the PDP context ID: `AT+QHTTPCFG="contextid",1`
2. Enable output of HTTP response headers: `AT+QHTTPCFG="responseheader",1`
3. Activate the PDP context if it is not already active: `AT+QIACT=1`
4. Select the SSL context ID for this PDP context ID: `AT+QHTTPCFG="sslctxid",1`
5. Set the SSL version. Choose TLS 1.2: `AT+QSSLCFG="sslversion",1,3`
6. Set the SSL cipher suite. Choose all types: `AT+QSSLCFG="ciphersuite",1,0xFFFF`
7. For testing, set the SSL verification level to `0`, i.e., no CA certificate is required: `AT+QSSLCFG="seclevel"=0`
8. Set the target URL: `AT+QHTTPURL=70`This sets the modem to receive, prompted by the output `CONNECT`. The parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of `70` comes from the URL below. The URL you provide must include the protocol, ie. `https://`.
9. Upon receiving `CONNECT`, enter the URL. For example: <https://twilio-cms-prod.s3.amazonaws.com/documents/super-sim-test.json>
10. Issue a `GET` request: `AT+QHTTPGET`
11. View the response: `AT+QHTTPREAD`

The request will look something like this:

```html
HTTP/1.1 200 OK
Date: Thu, 19 May 2022 10:23:25 GMT
Last-Modified: Thu, 19 May 2022 10:05:25 GMT
Accept-Ranges: bytes
Content-Type: application/json
Server: AmazonS3
Content-Length: 128

{
   "userId": 1,
   "id": 5,
   "title": "laboriosam mollitia et enim quasi adipisci quia provident illum",
   "completed": false,
}                                                                                                                         }
OK

+QHTTPREAD: 0
```

### Perform an HTTP(S) POST <a href="#perform-an-http-s--post-3" id="perform-an-http-s--post-3"></a>

Sending data from the modem to an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols: call `AT+QHTTPOST` instead of `AT+QHTTPGET`.

Optionally, the `QHTTPOST` command takes a parameter indicating the amount of data you are sending. The modem uses this to read that number of bytes via the UART over which your application is communicating with it. If you are providing a custom HTTP request header, remember to include its length too.

### Low-power modes <a href="#low-power-modes-3" id="low-power-modes-3"></a>

While the EG21-G supports low-power modes for eDRX and PSM, support for these features will vary by visited network and location. The commands to enable for each of these are:

```bash
AT+CEDRXS=1
AT+CPSMS=1
```

Using these features, but especially PSM, can make the modem inaccessible to the terminal during its sleep time. It's best to experiment with these features locally. To disable all power saving, send:

```bash
AT+CEDRXS=0
AT+CPSMS=0
```

You can learn more about implementing these modes in our [low-power usage documentation](https://docs.korewireless.com/en-us/supersim/cellular-module-knowledgebase/low-power-optimization-for-cellular-modules).

### Additional resources <a href="#additional-resources-3" id="additional-resources-3"></a>

• [EG25-G AT Commands Manual](https://www.quectel.com/product/lte-eg25-g/#specifications) - *Scroll down to the AT Commands section, login is required to download*