Modem Crashes after sending sms (3G+4G)

Teltonika Networks
1

Hello,

iam using a TRB140 to send notification via sms. It runs |Firmware version|TRB1_R_00.07.04.5|
| — | — |
|Kernel version|5.4.229|
The current problem we face is that the modem dies for at least 5 minutes when you try to send a message, doesn’t matter if it’s via GUI or GLI. Recieving messages is not working properly either…
Error looks like the following in our monitoring:
“Connection Status of Modem 1 is not CONNECTED: (Disconnected)”
AND “Net Status of Modem 1 is not REGISTERED: (Not registered)”
This happens each time using 4G or 3G.
I’ ve got it working using 2G, but that is no solution for the future… My Card definetly supports 4G…
Our Modem Settings are:
Deny data roamin: on
VoLTE Auto
Networktype: (was on Auto, tested 4G and 3G each, 2G ended up working)
Band selection: Auto
low signal reconnect: off
sms limt: on
sms limit ist 2000 → only 30/2000 have been sent yet…

3

Hello,

Could you please check if settings VoLTE manually to ON or OFF helps?

Also, could you please check what is the firmware version of the internal modem in Status → System?

It would be great if you could connect to TRB via CLI/SSH with username ‘root’, execute the ‘logread -f’ commnad to view logs in real-time, and then try sending SMS. Before sharing those logs, please hide you phone number and any other sensitive information, such as public IP addresses that may potentially appear in the logs.

Kind Regards,

4

Hello,

thanks in advanve for the reply.
Modem Firmware: EC25EUGAR06A05M4G_BETA1108_01.005.00.000
i typed logread -f as root but nothing seems to happen. I tried sending a sms via GUI, but the CLI didnt do anything just:
root@DeviceName:~# logread -f

Did i forget something or did something wrong?

EDIT: logread works… when i change the modem Config i get output there. But sending sms doesnt give an log output. I can see logs when I, for example, change the Modem to 4G or 2G…

5

Hello,

So the modem crashes when you send SMS, but there is nothing in the logs?

Can you share the output of the following command:

gsmctl -A "AT+CEER"

When you change VoLTE manually to ON/OFF, can you check its status via:

gsmctl -v

If it has not changed to Active/Inactive like you configured in the WebUI, try the following commands:

mctl -r

Then, allow it a few minutes to restart and check VoLTE status again with gsmctl -v command.

You can also try the following commands to see if you can send SMS after executing them (try one command at a time).

ubus call gsm.modem0 exec '{"command":"AT+CGSMS=1"}'

ubus call gsm.modem0 exec '{"command":"AT+QNVFW=\"/nv/item_files/modem/mmode/sms_domain_pref\",00"}'

Kind Regards,

6

Hello,

I’ve tested it… not helping

As 4G only ist configured

gsmctl -A “AT+CEER”
output: +CEER: 0,29

gsmctl -v
VoLTE ON: active
VoLTE off: Inactive

ubus call gsm.modem0 exec ‘{“command”:“AT+CGSMS=1”}’

After sms send(GUI says succesfull, but ther is nothing):
Internal modem

  • dBm
    Data connection
    Connected

State
N/A; N/A; N/A

Sim card info
N/A (SIM 1)

Bytes received / sent
615.2 KB / 72.2 MB

after a few minutes it recovers to:

Internal modem
-77 dBm

Data connection
Connected

State
Registered, home; vodafone.de; 4G (LTE)

Sim card info
Inserted (SIM 1)

Bytes received / sent
615.2 KB / 72.2 MB

After ubus call gsm.modem0 exec ‘{“command”:“AT+QNVFW="/nv/item_files/modem/mmode/sms_domain_pref",00”}’ same as above

Back to 2G, flawless delivery…

7

Hello,

Would it be possible for you to try sending SMS from the command line using the following commands and share the output?

gsmctl -S -s "0037011111111 testmessage"
ubus call gsm.modem0 send_sms '{"number":"003701111111","text":"testmessage2"}'

Also, would it be possible for you to test via different SIM card? Preferably win a SIM card from a different operator.

Another thing you can try is to reset the device to factory defaults in System → Backup, and without any additional configurations, try sending SMS again.

Kind Regards,

8

Hello AndzejJ,
I have tested a little bit, in CLI and 2G only sms work fine with a few tests, on Auto mode or 4G no output or sms… Logread -f didnt get me any output, strangely also no output or sms with 2G only.
Is there maybe a modem Update out there?

I testet some a week ago and got a log and some screenshots, but i am unable to Upload here, but you can follow this link to our Cloud: [redacted]

I try to test it with another sim, and i will also see if i can reset the device. I will reply later.

9

Hello,

A few things.

First of all, please avoid sharing troubleshoot files publicly, because anyone can download it and see information about your device.

Secondly, the logs do not indicate any issues. It seems that the device disconnects from the operator every 2 hours to get a new IP lease. The IP address is given by the operator for 2 hours, and after 2 hours the device disconnects and the operator gives a new IP address.

As for SMS, could you try the following command?:

ubus call gsm.modem0 set_mbn_select '{"mbn_name":"ROW_Generic_3GPP"}'

Then trying setting VoLTE manually to OFF/ON. If this does not help, switch back via:

ubus call gsm.modem0 set_mbn_select '{"mbn_name":"VF_Germany_VoLTE"}'

Lastly, once you reset the device and try a different SIM (preferably from a different operator), please let me know and we can continue troubleshooting further.

Kind Regards,

10

Hi there,

I deleted the troubleshoot file…

Thanks for your reply, I have tested these in different variations, in the end only 2G seemed to work, I logged my attempts in my link as 18_10_2023.txt…

Not wanting to give up, I reset everything back to how it was before:
VoLTE: Automatic
Network type: Auto
Band selection:Auto

I just tested for the sake of testing and it worked, not once… It worked with both of your last commands, also receiving, I can not understand…
There must be a reason, nothing has changed, it looks exactly the same as when I had the problems, I was sending small texts
I also tested with longer texts maxing out the limit, with that I could send 3 texts with maximum capacity before the modem went down… is this a bug or hardware limited and not fixable? aLSO when the modem went dead for some time the other messages I sent while it was “dead” were not sent when it came back and were gone, which is a big problem for us. Isn’t there some kind of robust queue that will send the SMS later if the modem times out? We use the SMS function with our monitoring for important notifications, it would be critical if we did not get all the messages sent. The instability is a huge problem, we have to rely on it, these settings above have not worked for us since I started this post, so I dont think this is a final solution.
Right now the problem isnt even recreateable and i feel this is more a problem with the modem which just cant handle so many rapid requests at once… But I have no clue why it now works with 4G and VoLTE, is there maybe a modem Update i can do?

I saw this post closes tomorrow, what happens if it isn’t resolved? If it doesn’t work like before, I will sure try to reset it but right now I am unable to test… The Modem still crashes, but not like it did before, just a few seconds / minutes, then it works again… I am just perplexed at this point, I will watch if the modem has problems the next couple of days/ next week via our monitoring and the i will see…

Thank you for your time and help!

11

Hello,

The timer has been extended.

If the device simply started working with the default settings, it is hard to say what was the issue. Could you please tell how many SMS messages and how rapidly are you trying to send? It is recommended to send SMS messages with at least 5 second intervals, otherwise there can potentially be issues.

Do you have other SMS related configurations on the device, such as alarms, etc?

Have you tried resetting the device to factory defaults and see if SMS messages are sent properly?

Kind Regards,

12

Hello,

thank you for your effort and help. Here are my extended tests and also at the end I factory resetted the device. I am afraid to say that I think this device is not able to handle our requirements.
FYI, I had to edit my APN from vodafon.de to vodafon,de becauase the forum detects this as links and two links are my maximum.

#####18_10_2023#####

changing to 4G VoLTE off logread outputs again and modem goes to this. After i try to send the the modem is dead again and no sms came

Wed Oct 18 10:37:15 2023 kern.info kernel: simcard configuration has been changed
Wed Oct 18 10:37:16 2023 daemon.info mobifd: Service reload initiated
Wed Oct 18 10:37:16 2023 daemon.err mobifd: [gsm.modem0] Failed to get usbnet mode
Wed Oct 18 10:37:21 2023 daemon.info mobifd: [gsm.modem0] SMS storage: sm
Wed Oct 18 10:37:21 2023 daemon.info mobifd: [gsm.modem0] VoLTE was succesfully set
Wed Oct 18 10:37:21 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 15 seconds of timeout
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] Connected to operator ‘vodafone,de’
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] -CFUN- Functionality: “Full”
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] -COPS- Mode: “Auto”, operator: “vodafone,de”
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] -CREG- Mode: “Enabled (with location information)”, status: “Registered, home”, LAC: “44212”, cell ID: “10255886”, technology: “E-UTRAN”
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] -CGREG- Mode: “Enabled (with location information)”, status: “Registered, home”, LAC: “44212”, cell ID: “10255886”, technology: “E-UTRAN”
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] -CEREG- Mode: “Enabled (with location information)”, status: “Registered, home”, LAC: “44212”, cell ID: “10255886”, technology: “E-UTRAN”
Wed Oct 18 10:37:26 2023 daemon.info mobifd: [gsm.modem0] IP address on PDP context “1”: “100.101.236.35”
Wed Oct 18 10:37:26 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is setting up now
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): Starting network mob1s1a1 using APN: web,vodafone,de
Wed Oct 18 10:37:26 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --set-client-id wds,1 --release-client-id wds --modify-profile --profile-identifier 3gpp,1 --profile-name profile1 --roaming-disallowed-flag yes --auth-type none --apn web,vodafone,de --pdp-type ip
Wed Oct 18 10:37:26 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --get-client-id wds
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): 1
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): cid4: 1
Wed Oct 18 10:37:26 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --set-ip-family ipv4 --set-client-id wds,1
Wed Oct 18 10:37:26 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --set-client-id wds,1 --start-network --apn web,vodafone,de --profile 1 --auth-type none --username --password
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): pdh4: -2027593920
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): -2027593920
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): Setting up rmnet0
Wed Oct 18 10:37:26 2023 daemon.notice netifd: mob1s1a1 (31053): Setting MTU: 1500 on rmnet0
Wed Oct 18 10:37:26 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is now up
Wed Oct 18 10:37:26 2023 daemon.notice netifd: Network device ‘rmnet0’ link is up
Wed Oct 18 10:37:27 2023 daemon.notice netifd: mob1s1a1 (31053): Setting up rmnet0 V4 DCHP
Wed Oct 18 10:37:27 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is enabled
Wed Oct 18 10:37:27 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ has link connectivity
Wed Oct 18 10:37:27 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is setting up now
Wed Oct 18 10:37:27 2023 daemon.notice netifd: mob1s1a1_4 (31219): udhcpc: started, v1.34.1
Wed Oct 18 10:37:27 2023 daemon.notice netifd: mob1s1a1_4 (31219): udhcpc: broadcasting discover
Wed Oct 18 10:37:27 2023 daemon.notice netifd: mob1s1a1_4 (31219): udhcpc: broadcasting select for 100.101.236.35, server 100.101.236.36
Wed Oct 18 10:37:27 2023 daemon.notice netifd: mob1s1a1_4 (31219): udhcpc: lease of 100.101.236.35 obtained from 100.101.236.36, lease time 7200
Wed Oct 18 10:37:27 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (rmnet0)
Wed Oct 18 10:37:27 2023 daemon.info mobifd: Auto APN is disabled on “mob1s1a1”. Skipping Ping To DNS functionality
Wed Oct 18 10:37:27 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is now up
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain test
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain onion
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain localhost
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain local
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain invalid
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain bind
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain lan
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using nameserver 10.1.1.1#53
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using nameserver 139.7.30.125#53
Wed Oct 18 10:37:27 2023 daemon.info dnsmasq[6550]: using nameserver 139.7.30.126#53
Wed Oct 18 10:37:27 2023 daemon.emerg quota_limit: Set up nftables quota limit on rmnet0 (mob1s1a1)
Wed Oct 18 10:37:28 2023 daemon.info dnsmasq[6550]: read /etc/hosts - 4 addresses
Wed Oct 18 10:37:28 2023 daemon.info dnsmasq[6550]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Wed Oct 18 10:37:29 2023 kern.info Mobile data connected (internal modem)
Wed Oct 18 10:37:29 2023 kern.info Joined LTE network (internal modem)
Wed Oct 18 10:37:29 2023 kern.info Connected to vodafone,de operator (internal modem)
Wed Oct 18 10:37:29 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (rmnet0)
Wed Oct 18 10:37:30 2023 daemon.info dnsmasq[6550]: read /etc/hosts - 4 addresses
Wed Oct 18 10:37:30 2023 daemon.info dnsmasq[6550]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Wed Oct 18 10:37:30 2023 kern.info Mobile data connected (internal modem)
Wed Oct 18 10:37:30 2023 kern.info Joined LTE network (internal modem)
Wed Oct 18 10:37:30 2023 kern.info Connected to vodafone,de operator (internal modem)
Wed Oct 18 10:37:34 2023 daemon.info procd: Instance ntpclient::instance1 pid 10639 not stopped on SIGTERM, sending SIGKILL instead

Internal modem -76 dBm
Data connection
Connected
State
Registered, home; vodafone,de; 4G (LTE)
Sim card info
Inserted (SIM 1)
Bytes received / sent
1006.8 KB / 72.6 MB

after sms send attempt

Internal modem - dBm
Data connection
Connected
State
N/A; N/A; N/A
Sim card info
N/A (SIM 1)
Bytes received / sent
1006.8 KB / 72.6 MB

Meanwhile logread does not ouput anything…
when I switch to 4G VoLTE on after it cought itself again

Internal modem
-76 dBm
Data connection
Connected
State
Registered, home; vodafone,de; 4G (LTE); VoLTE
Sim card info
Inserted (SIM 1)
Bytes received / sent
1006.5 KB / 72.6 MB

after sms sending(not succesfull), same old. Logread -f no output, only when i change sim configs…

Internal modem

  • dBm
    Data connection
    Connected
    State
    N/A; N/A; N/A
    Sim card info
    N/A (SIM 1)
    Bytes received / sent
    1006.5 KB / 72.6 MB

switching to Auto, VoLTE Auto:

root@IBNDJU05:~# logread -f
Wed Oct 18 12:00:58 2023 kern.info kernel: simcard configuration has been changed
Wed Oct 18 12:00:59 2023 daemon.info mobifd: Service reload initiated
Wed Oct 18 12:00:59 2023 daemon.info mobifd: [gsm.modem0] Config reload initiated
Wed Oct 18 12:00:59 2023 daemon.err mobifd: [gsm.modem0] Failed to get usbnet mode
Wed Oct 18 12:01:00 2023 daemon.notice netifd: mob1s1a1 (12956): Stopping network mob1s1a1
Wed Oct 18 12:01:00 2023 daemon.notice netifd: mob1s1a1 (12956): Stopping network on /dev/cdc-wdm0!
Wed Oct 18 12:01:00 2023 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,1 --stop-network 0xFFFFFFFF --autoconnect
Wed Oct 18 12:01:00 2023 daemon.notice netifd: mob1s1a1 (12956): Releasing client-id 1 on /dev/cdc-wdm0
Wed Oct 18 12:01:00 2023 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,1 --release-client-id wds
Wed Oct 18 12:01:00 2023 daemon.notice netifd: mob1s1a1 (12956): Command failed: Not found
Wed Oct 18 12:01:00 2023 daemon.notice netifd: mob1s1a1_4 (3727): udhcpc: received SIGTERM
Wed Oct 18 12:01:00 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is now down
Wed Oct 18 12:01:00 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ has link connectivity loss
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain test
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain onion
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain localhost
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain local
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain invalid
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain bind
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain lan
Wed Oct 18 12:01:00 2023 daemon.info dnsmasq[6550]: using nameserver 10.1.1.1#53
Wed Oct 18 12:01:00 2023 daemon.notice netifd: mob1s1a1 (12956): Command failed: Permission denied
Wed Oct 18 12:01:00 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is now down
Wed Oct 18 12:01:01 2023 daemon.info dnsmasq[6550]: read /etc/hosts - 4 addresses
Wed Oct 18 12:01:01 2023 daemon.info dnsmasq[6550]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Wed Oct 18 12:01:01 2023 kern.info Mobile data disconnected (internal modem)
Wed Oct 18 12:01:04 2023 daemon.info mobifd: [gsm.modem0] SMS storage: sm
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 15 seconds of timeout
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] Connected to operator ‘vodafone,de’
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] -CFUN- Functionality: “Full”
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] -COPS- Mode: “Auto”, operator: “vodafone,de”
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] -CREG- Mode: “Enabled (with location information)”, status: “Registered, home”, LAC: “44212”, cell ID: “10255886”, technology: “E-UTRAN”
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] -CGREG- Mode: “Enabled (with location information)”, status: “Registered, home”, LAC: “44212”, cell ID: “10255886”, technology: “E-UTRAN”
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] -CEREG- Mode: “Enabled (with location information)”, status: “Registered, home”, LAC: “44212”, cell ID: “10255886”, technology: “E-UTRAN”
Wed Oct 18 12:01:05 2023 daemon.info mobifd: [gsm.modem0] IP address on PDP context “1”: “100.70.230.20”
Wed Oct 18 12:01:05 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is setting up now
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): Starting network mob1s1a1 using APN: web,vodafone,de
Wed Oct 18 12:01:06 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --set-client-id wds,1 --release-client-id wds --modify-profile --profile-identifier 3gpp,1 --profile-name profile1 --roaming-disallowed-flag yes --auth-type none --apn web,vodafone,de --pdp-type ip
Wed Oct 18 12:01:06 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --get-client-id wds
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): 1
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): cid4: 1
Wed Oct 18 12:01:06 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --set-ip-family ipv4 --set-client-id wds,1
Wed Oct 18 12:01:06 2023 user.notice netifd: uqmi -d /dev/cdc-wdm0 --timeout 30000 --set-client-id wds,1 --start-network --apn web,vodafone,de --profile 1 --auth-type none --username --password
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): pdh4: -2027140784
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): -2027140784
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): Setting up rmnet0
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): Setting MTU: 1500 on rmnet0
Wed Oct 18 12:01:06 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is now up
Wed Oct 18 12:01:06 2023 daemon.notice netifd: Network device ‘rmnet0’ link is up
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1 (13357): Setting up rmnet0 V4 DCHP
Wed Oct 18 12:01:06 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is enabled
Wed Oct 18 12:01:06 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ has link connectivity
Wed Oct 18 12:01:06 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is setting up now
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1_4 (13526): udhcpc: started, v1.34.1
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1_4 (13526): udhcpc: broadcasting discover
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1_4 (13526): udhcpc: broadcasting select for 100.70.230.20, server 100.70.230.21
Wed Oct 18 12:01:06 2023 daemon.notice netifd: mob1s1a1_4 (13526): udhcpc: lease of 100.70.230.20 obtained from 100.70.230.21, lease time 7200
Wed Oct 18 12:01:06 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1 (rmnet0)
Wed Oct 18 12:01:06 2023 daemon.info mobifd: Auto APN is disabled on “mob1s1a1”. Skipping Ping To DNS functionality
Wed Oct 18 12:01:06 2023 daemon.notice netifd: Interface ‘mob1s1a1_4’ is now up
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain test
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain onion
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain localhost
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain local
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain invalid
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain bind
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using only locally-known addresses for domain lan
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using nameserver 10.1.1.1#53
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using nameserver 139.7.30.125#53
Wed Oct 18 12:01:06 2023 daemon.info dnsmasq[6550]: using nameserver 139.7.30.126#53
Wed Oct 18 12:01:07 2023 daemon.emerg quota_limit: Set up nftables quota limit on rmnet0 (mob1s1a1)
Wed Oct 18 12:01:08 2023 daemon.info dnsmasq[6550]: read /etc/hosts - 4 addresses
Wed Oct 18 12:01:08 2023 daemon.info dnsmasq[6550]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Wed Oct 18 12:01:08 2023 kern.info Mobile data connected (internal modem)
Wed Oct 18 12:01:08 2023 kern.info Joined LTE network (internal modem)
Wed Oct 18 12:01:08 2023 kern.info Connected to vodafone,de operator (internal modem)
Wed Oct 18 12:01:08 2023 user.notice firewall: Reloading firewall due to ifup of mob1s1a1_4 (rmnet0)
Wed Oct 18 12:01:09 2023 daemon.info dnsmasq[6550]: read /etc/hosts - 4 addresses
Wed Oct 18 12:01:09 2023 daemon.info dnsmasq[6550]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Wed Oct 18 12:01:09 2023 kern.info Mobile data connected (internal modem)
Wed Oct 18 12:01:09 2023 kern.info Joined LTE network (internal modem)
Wed Oct 18 12:01:09 2023 kern.info Connected to vodafone,de operator (internal modem)
Wed Oct 18 12:01:13 2023 daemon.info procd: Instance ntpclient::instance1 pid 4473 not stopped on SIGTERM, sending SIGKILL instead

Internal modem
-75 dBm
Data connection
Connected
State
Registered, home; vodafone,de; 4G (LTE); VoLTE
Sim card info
Inserted (SIM 1)
Bytes received / sent
1004.1 KB / 72.6 MB

sms wasnt send again, no further logread output

modem like this again:
Internal modem

  • dBm
    Data connection
    Connected
    State
    N/A; N/A; N/A
    Sim card info
    N/A (SIM 1)
    Bytes received / sent
    1004.1 KB / 72.6 MB

#####20_10_2023 Further testing######

Today, sending messages up to less then 160 characters still works like a charm, sending bigger like 3 sms maxed out it gets slow, the modem disconnects (not good).
I talked to my boss about the current situation: The sms we need to send are about 600->1000+ characters, so about 5-10 sms per alert, it seems this system is just not capable of that.
I reset the device to its default and tested, the same problems, as you can see below, I tested with many characters, I recieved most of them, but some did not make it, which is absolutely unacceptable in our use case.
At the end I tried to send a small sms “gsmctl -S -s “015735277405 -----””, nothing special, but this is where the modem broke down completely, just like when I started this topic → error message: [gsmctl_send_sms:20] Error: ERROR: Failed to parse response
The device went back to all N/A for many minutes. And I did not recieve the message…
Other sim same problem.
I am reaching the point where this is not a bug, but the device is simply not capable of this kind of load, we purchased this business solution in order to get a reliable system to notify us (mostly at night) when there is an important monitoring alert,
also we wish the whole alert can be sent in that sms, no matter if it is 3 sms long or up to 10 sms (one sms 160 characters). Is there a way to make this work with this device or do we need something else?
The device needs to be reliable and able to send bigger notfications from our Zabbix, if that is not the case this device is not useable for us I am afraid.

root@TRB140:~# gsmctl -S -s "015735277405 --------------------------------------------------------------------------------------------------------

---------------------------------------------------11"
SMS sent: 3
root@TRB140:~# gsmctl -S -s "015735277405 --------------------------------------------------------------------------------------------------------

---------------------------------------------------11----------------------------------

^C
root@TRB140:~# gsmctl -S -s "015735277405 --------------------------------------------------------------------------------------------------------

---------------------------------------------------11----------------------------------
^C
root@TRB140:~# gsmctl -S -s "015735277405 --------------------------------------------------------------------------------------------------------

---------------------------------------------------11---------------------------------"
SMS sent: 4
root@TRB140:~# gsmctl -S -s "015735277405 -------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------^C
root@TRB140:~# gsmctl -S -s "015735277405 -------------------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------------------------------------------------------11----------------
-----------------1

"
SMS sent: 4
root@TRB140:~# gsmctl -S -s "015735277405 -------------------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------------------------------------------------------11----------------
----------------2"
SMS sent: 4
root@TRB140:~# --------------------------------------------------------------------------------------------------------------------------------------
-ash: --------------------------------------------------------------------------------------------------------------------------------------: not found
root@TRB140:~# ----------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------11-
------------------------------------------------------------------------------1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
111111111111111111
-ash: --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------11-------------------------------------------------------------------------------1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111: Filename too long

root@TRB140:~# gsmctl -S -s “015735277405 -----”
[gsmctl_send_sms:20] error: ERROR: Failed to parse response

Kind Regards,

13

Hello,

Is my understanding correct that you are able to send a few SMS messages, but the issues arise when you send many messages? If so, it is probably because the modem is unable to properly process so many messages. You should allow around 5 seconds for each message. The modem can have issues if you try sending too many messages in quick succession. When sending multi-part SMS, there is additional header information, which means that the length of each message within a multi-part SMS is less than 160 characters.

Are you on the v7.05 firmware?

Kind Regards,

14

Hello,

Yes, I can send short messages of less than 160 characters without any problem. However, we only send larger SMS, which are at least 5 times the size, usually more. We don’t manually send these notifications, our Monitoring does and decreasing them is no option.

  1. The system cuts longer messages apart, which is a bummer.
  2. Is there a device that can handle more SMS length?
    The Modem has problems handling large sms, which in our case is almost every message, these are error messages with up to 1500+ characters, is there a way to get this to work? So we need bigger multi-part SMS, I guess, because three is the limit of this device.

-I did the firmware update this morning, I did not check again because when we started the device was up to date…

An interesting bug appeared over the weekend, the unit would disconnect every two minutes, which was quite annoying…

[07:38:01] [Connection Status of Modem 1 is not CONNECTED: (Disconnected)]
[07:37:56] [Net Status of Modem 1 is not REGISTERED: (Searching)]
[07:34:01] [Connection Status of Modem 1 is not CONNECTED: (Disconnected)]
[07:33:56] [Net Status of Modem 1 is not REGISTERED: (Searching)]
[07:25:56] [Net Status of Modem 1 is not REGISTERED: (Searching)]
etc.

But they seem stable again

15

Hi,
two thoughts on this:

  1. we always turn OFF VoLTE because we don’t use Voice on our routers
  2. SMS are limited to 160 characters per GSM standard, there’s no way around this

The modem therefore breaks up longer messages into chunks.

The moment you exceed the 160 characters your are limited to 153 characters per SMS
because the remaining seven bytes are used for linking the messages together.

If you’re using UTF charset you’re even limited to 70 (UTF-)characters per SMS.

There also seems to be a limit of 5000 characters in total per large message but I was
unable to verify that and this can as well be a limitation of a specific modem.

Anyway, we had an incident with a fire alarm system which sent 120,000 SMS with error
messages and false alarms due to a flooding, all below 160 characters, and that did
work out perfectly (unfortunately, because it took us three days until we were able to
reset the system and clear the remaining messages). That was REAL fun!

Just my 2 cents.

Regards,
Timelapse Admin

16

Hello,

thanks for the reply, i think i will test the System for a few weeks with VoLTE off then. I hope I understand your second point correct, even larger Messages get send normally, just cut in half?
As long as the whole Message gets send it is no problem, they tend to be rarely send and mostly for nights.

Kind Regards

17

Hi,
just another quick answer before the topic closes.

You wrote:

I hope I understand your second point correct, even larger Messages get send normally,
just cut in half?

Yes, you’re basically correct.

If you send 160 characters it gets sent as one SMS.
If you send 161 characters it gets sent as one SMS wit 153 characters and 7 characters
“link info” and a second sms with the remaining 7 characters.

140 byte times 8 bit can contain 160 characters consisting of 7 bit each.
See e.g. this link: (GSM and Unicode SMS length)

If you prefer more in-depth information about the GSM alphabet (ETSI GSM 03.38) and the
“allowed” characters look here: (Long SMS Text Messages and the 160 Character Limit | NowSMS)

Regards,
Timelapse Admin

18

This topic was automatically closed after 22 days. New replies are no longer allowed.

19
20

This topic was automatically closed after 4 days. New replies are no longer allowed.