Hello, I’m testing modem eg915u tcp server mode but server not working as well on 4G LTE network
modem gets public IP but gets pdpdeact , Is this firmware problem?
modem gets public IP but gets pdpdeact , Is this firmware problem?
Dear Romaro,
Thank you for reaching out.
From your screenshot of AT logs we can see the following sequence:
AT+CPIN? → +CPIN: READY
AT+CGREG? → +CGREG: 0,2
AT+CEREG? → +CEREG: 0,2
AT+QICSGP=1,1,"beeline.internet.uz","","",1
AT+QIACT=1 → OK
AT+QIACT? → +QIACT: 1,1,1,"<public IPv4>"
+QIURC: "pdpdeact",1
+QIURC: "pdpdeact",1 means that PDP context ID 1 has been deactivated by the network side, not by the module itself. Once this URC appears, the data bearer for CID 1 is already down, so any subsequent socket operation (such as AT+QIOPEN for TCP LISTENER) will fail. This matches the +QIOPEN: 0,561 result you see later.
Because the PDP is terminated immediately after activation, this behaviour is more consistent with APN/SIM or network policy rather than a pure EG915U firmware defect. Typical causes include:
- APN or SIM profile that does not allow persistent PDP sessions or inbound TCP connections.
- Firewall / CGNAT policy on the operator’s side that tears down the session.
- Temporary problem on the LTE network for that APN.
To move forward, could you please:
- Confirm PDP state and error cause right after
pdpdeact
Run these commands immediately after the URC:
AT+CEER
AT+CGACT?
AT+QIACT?
This helps confirm that CID 1 is indeed inactive and gives the network-reported cause.
- Retest with the recommended TCP LISTENER format
For example:
AT+QICSGP=1,1,"beeline.internet.uz","","",1
AT+QIACT=1
AT+QIOPEN=1,0,"TCP LISTENER","127.0.0.1",0,4010,0
(For TCP LISTENER the remote port should be 0, and 4010 is the local listening port.)
- Check with your operator / try another APN or SIM
Please confirm with Beeline that:
- The APN
beeline.internet.uzfor your SIM supports a public IPv4 PDP with inbound TCP connections, or - If a special M2M / static IP APN is required for this use case.If possible, test the same module and script with:
- Another APN from Beeline (e.g. M2M/business APN), or
- A SIM from a different operator.
- Verify simple client data first
Before using server mode, please check that normal client traffic is stable:
AT+QICSGP=1,1,"beeline.internet.uz","","",1
AT+QIACT=1
AT+QPING=1,"8.8.8.8"
If PDP is also deactivated shortly after this simple test, it strongly indicates a network/APN configuration issue.
Additionally, please share:
- Module firmware version (
ATI/AT+QGMR) - The full AT log from registration →
QIACT→pdpdeact→QIOPEN
With this information we can confirm whether there is any abnormal modem behaviour, but based on the current AT logs it looks like network-initiated PDP release, not a TCP server firmware problem.
Thank you.
Best Regards,
Aghelan
+QIURC: “pdpdeact”,1
AT+CEER
+CEER: 0,-1
OK
AT+CGACT?
+CGACT: 1,0
OK
AT+QIACT?
OK
AT+CGACT?
+CGACT: 1,0
Dear Romaro,
Thanks for the new AT log snippet.
+QIURC: "pdpdeact",1 together with CEER: 0,-1, CGACT: 1,0 and AT+QIACT? returning only OK means, with certainty, that PDP context 1 has already been dropped and there is no active IP context when you try to use the TCP server.
This is why QIOPEN fails, the bearer is gone, not the TCP-server feature itself.
Please re-activate data with AT+QIDEACT=1 → AT+QICSGP → AT+QIACT=1, and in parallel check with your operator whether the current APN/SIM profile really supports a stable public IPv4 PDP and incoming TCP connections (or test with another APN/SIM) to find the exact network-side cause.
Kindly share the full AT command sequence from power-on/registration up to the pdpdeact URC, and also the module firmware information by running ATI and AT+CGMR and sending us the output.
Best Regards,
Aghelan
ATI
Quectel
EG915U
Revision: EG915UEUABR03A01M08
OK
AT+CGMR
EG915UEUABR03A01M08
OK
AT+QICSGP=1,1,“internet.beeline.uz”,“”,“”,0
OK
AT+QIACT=1
OK
AT+QIACT?
+QIACT: 1,1,1,“xx.xx.xx.xx”
OK
+QIURC: “pdpdeact”,1
AT+QIDEACT=1
OK
AT+QICSGP=1,1,“internet.beeline.uz”,“”,“”,0
OK
AT+QIACT=1
OK
AT+QIACT?
+QIACT: 1,1,1,“xx.xx.xx.xx”
OK
+QIURC: “pdpdeact”,1
Dear Romaro,
Thank you for providing the AT logs.
From your sequence we see that PDP context 1 is configured and activated correctly (QIACT returns an IPv4 address), and then the module immediately reports +QIURC: "pdpdeact",1 even before any socket commands, which means the context is being released by the network, not by EG915U firmware. According to the Quectel TCP/IP note, +QIURC: "pdpdeact" specifically indicates “PDP context may be deactivated by the network”, and the host can only re-run AT+QIDEACT/AT+QIACT or change APN/SIM profile in this case.
Please check with Beeline that the APN internet.beeline.uz and your SIM plan allow a stable data session (with public IPv4, if needed) and, if possible, test with another APN or SIM; if the same behaviour appears on a different network, please share the full log from registration to pdpdeact so we can investigate further.
Best Regards,
Aghelan
Hello! there are full logs
Dear Romaro,
Thank you for providing the full logs.
Kindly accept my permission request to view the logs.
Thank you.
Best Regards,
Aghelan
Hello, Now you could access to link
Dear Romaro,
Thank you for allowing us to access the link.
I received the logs successfully.
Best Regards,
Aghelan