EG25-G doesn't stay connected to network after traffic stops passing through module

Technical Subjects Driver
1

Hi, I’m having an issue with the EG25-G in Germany with a Vodafone SIM. I’m able to connect to the network and use the SIM no problem. However, after I stop passing traffic through the device, it seems to go into a lower power state, such that when I try to pass traffic through the module again, the device no longer transmits. The device seems to change from a connected state to a connecting state.

Firmware revision: EG25GGBR07A08M2G

Has anyone seen this before? What can I do to fix it?

Thanks

2

Here’s a generic config I’m using to test in Canada (our customer is in Germany, I’m in Canada)

mmcli -m 0

General | dbus path: /org/freedesktop/ModemManager1/Modem/0
| device id: a2b90774ec95a440fd4b4543bdc26fe48a81f432

Hardware | manufacturer: QUALCOMM INCORPORATED
| model: QUECTEL Mobile Broadband Module
| firmware revision: EG25GGBR07A08M2G
| carrier config: Telus-Commercial_VoLTE
| carrier config revision: 05800C43
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 867698043735359

System | device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.2
| drivers: option1, qmi_wwan
| plugin: Quectel
| primary port: cdc-wdm0
| ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB2 (at), wwan0 (net),
| ttyUSB3 (at)

Numbers | own: 1778201**** (starred out to remove personal info)

Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: registered
| power state: on
| access tech: lte
| signal quality: 47% (recent)

Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g; preferred: 3g
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: 2g
| allowed: 3g, 4g; preferred: 3g
| allowed: 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 2g
| current: allowed: 2g, 3g, 4g; preferred: 4g

Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5,
| utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39,
| eutran-40, eutran-41, utran-19
| current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5,
| utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39,
| eutran-40, eutran-41, utran-19

IP | supported: ipv4, ipv6, ipv4v6

3GPP | imei: 86769804373**** (starred out to remove personal info)
| operator id: 302220
| operator name: TELUS
| registration: home

3GPP EPS | ue mode of operation: csps-1

SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0

Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/0

3

When the connection is found to be disconnected, the dial-up must be initiated again and the network data connection is re-established.

4

How to do dail-up? I am also facing the same issue in linux