TCP Socket not opening on RG500

IoT Modules 5G Module
,
1

Hello, we are using a RG500Q-EA module on a network in which we have two applications. In the first one we use modemmanager to manage the connection and the module is working correctly. On the second application we need to use AT commands to open a TCP socket and it is failing to open. Additionally, pinging the server is not successful. From the modem working with modemmanager both operations are completing. These are the AT commands we are using:

AT+C5GREG?
+C5GREG: 2,1,"1FA5","B3B101",11,0,""

AT+QENG="servingcell"
+QENG: "servingcell","NOCONN","NR5G-SA","TDD",999,40,B3B101,29,1FA5,475970,40,3,-74,-11,22,1,-

AT+QIACT=1
OK

AT+QIACT?
+QIACT: 1,1,1,"172.26.1.241"

AT+QIOPEN=1,2,"TCP","88.30.42.137",1887,0,1
OK
+QIOPEN: 2,566

AT+QPING=1,"88.30.42.137",10,10
OK
+QPING: 558

How could we troubleshoot the connection in the modem that is not working? Thank you in advance.

2

Dear @CarlosR_5COMM
Please share your current firmware.
Did you use the same PDP context id for the two application?
In modemmanager, did you have TCP or other operation?

3

Hello Silvia, the firmware version is RG500QEAAAR11A06M4G. We did activate the same context on both setups. Additionally, in the setup that is not working, we tried to configure and activate a different context id but still didn’t get connectivity. In the modemmanager setup we achieved full internet connectivity, including testing the connection with the server at 88.30.42.137, both ping and opening TCP sockets.

4

Dear @CarlosR_5COMM
It is better to capture a wireshark log to check the reason.
Please share your whole operations.

In the first one we use modemmanager to manage the connection and the module is working correctly.
=>How do you do like this?