Unable to send SMS on GL-X3000

My GL-X3000 router doesnt seem to be able to send SMS messages. It recieves them fine and the cellular connection works perfectly. But when i try to send messages i get a spinning timer and then just a red warning symbol. My firmware version is 0600snapshot1 and the carrier is Vodafone Ireland. Any recommended debugging steps would be appreciated

Thanks in advance!

Maybe you need to fix the mms settings.

Thanks for the quick response @SpitzAX3000

I dont see any MMS settings. Is there any guides you could point me to.

Thanks

NeByr,

I’m curious, why are you trying to send an SMS from the sim card in your router? Wouldn’t your phone be eaiser?

Eric

Yes @EricG but it’s more for pay as you go comms with the carrier such as balance enquiries, top ups and low credit warnings.

If you insert the sim in your phone can you send sms ? Is the sms call center number set correctly ?

Yeah works fine from my mobile phone. I’ve tried many variations of multiple phone numbers. I’m struggling to find any error messages in the log

AT+CPMS?
AT+CGDCONT?
AT+CGPADDR
Can you run this command to see

1 Like

AT+CPMS replies ERROR

AT+CGDCONT replies OK

AT+CGPADDR replies…
+CGPADDR: 1,β€œ10.143.202.147”
+CGPADDR: 2,β€œ10.195.163.9”
+CGPADDR: 3,β€œ0.0.0.0”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
+CGPADDR: 4,β€œ0.0.0.0”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
+CGPADDR: 5,β€œ0.0.0.0”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
OK

This is the issue! It should return like this;

+CPMS: β€œME”,0,255,β€œME”,0,255,β€œME”,0,255

OK

Try to fix it:

AT+CPMS=β€œME”,β€œME”,β€œME”

@ywp thanks for hints!!

Sorry I messed up, I have been educating myself on these commands and only see now that the first 2 you suggested were AT commands with a question mark. The last outputs I sent in the previous message were without the quesiton marks. The correct response should have been

AT+CPMS?
+CPMS: β€œME”,0,255,β€œME”,0,255,β€œME”,0,255

AT+CGDCONT?
+CGDCONT: 1,β€œIPV4V6”,β€œlive.vodafone.com”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,β€œβ€,0
+CGDCONT: 2,β€œIPV4V6”,β€œims”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,β€œβ€,0
+CGDCONT: 3,β€œIPV4V6”,β€œhos”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,β€œβ€,0
+CGDCONT: 4,β€œIPV4V6”,β€œsos”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,1,β€œβ€,0
+CGDCONT: 5,β€œIPV4V6”,β€œweb.vodafone.de”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,β€œβ€,0

AT+CGPADDR
+CGPADDR: 1,β€œ10.143.202.147”
+CGPADDR: 2,β€œ10.195.163.9”
+CGPADDR: 3,β€œ0.0.0.0”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
+CGPADDR: 4,β€œ0.0.0.0”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”
+CGPADDR: 5,β€œ0.0.0.0”,β€œ0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”

So I think the prefferred message storage looks ok.

Yes it look ok. Can you try to send sms again and check the logs for any errors ?

Heres the recent log around the time I sent a test message. I have removed some repetative lines for brevity. I notice theres a line mentioning an error referencing sending the message.

Tue Apr 23 16:50:34 2024 kern.notice kernel: [1994090.588498] 7981@C08L3,ap_peer_auth_req_at_idle_action() 717: AUTH - MBSS(0), Rcv AUTH seq#1, Alg=0, Status=0 from [wcid=2]4c:55:cc:1b:45:ce
Tue Apr 23 16:50:34 2024 kern.notice kernel: [1994090.606430] 7981@C08L3,ap_cmm_peer_assoc_req_action() 1647: Recv Assoc from STA - 4c:55:cc:1b:45:ce
Tue Apr 23 16:50:34 2024 kern.notice kernel: [1994090.615891] 7981@C08L3,ap_cmm_peer_assoc_req_action() 2170: ASSOC Send ASSOC response (Status=0)…
Tue Apr 23 16:50:34 2024 kern.notice kernel: [1994090.625138] 7981@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0
Tue Apr 23 16:50:34 2024 kern.notice kernel: [1994090.631743] 7981@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0
Tue Apr 23 16:50:35 2024 kern.notice kernel: [1994090.746410] 7981@C15L3,WPABuildPairMsg1() 5280: <=== send Msg1 of 4-way
Tue Apr 23 16:50:35 2024 kern.notice kernel: [1994090.753258] 7981@C15L3,PeerPairMsg2Action() 6202: ===>Receive msg 2
Tue Apr 23 16:50:35 2024 kern.notice kernel: [1994090.760286] 7981@C15L3,WPABuildPairMsg3() 5557: <=== send Msg3 of 4-way
Tue Apr 23 16:50:35 2024 kern.notice kernel: [1994090.767083] 7981@C15L3,PeerPairMsg4Action() 6632: ===>Receive msg 4
Tue Apr 23 16:50:35 2024 kern.warn kernel: [1994090.779127] 7981@C15L2,PeerPairMsg4Action() 6994: AP SETKEYS DONE(ra0) - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=2 from 4c:55:cc:1b:45:ce
Tue Apr 23 16:50:35 2024 kern.warn kernel: [1994090.779127]
Tue Apr 23 16:50:39 2024 daemon.info dnsmasq-dhcp[4204]: DHCPDISCOVER(br-lan) 4c:55:cc:1b:45:ce
Tue Apr 23 16:50:39 2024 daemon.info dnsmasq-dhcp[4204]: DHCPOFFER(br-lan) 192.168.8.103 4c:55:cc:1b:45:ce
Tue Apr 23 16:50:39 2024 daemon.info dnsmasq-dhcp[4204]: DHCPREQUEST(br-lan) 192.168.8.103 4c:55:cc:1b:45:ce
Tue Apr 23 16:50:39 2024 daemon.info dnsmasq-dhcp[4204]: DHCPACK(br-lan) 192.168.8.103 4c:55:cc:1b:45:ce HubController-5CE
Tue Apr 23 16:51:10 2024 daemon.err modem_AT: (modem_AT.c:350) send_msg: AT+CMGS=18,0011000C915383672952470000FF04D4F29C0E
; len = 41
Tue Apr 23 16:52:34 2024 daemon.info eco[2321]: (gl-ngx-session:459) del ws
Tue Apr 23 16:52:35 2024 daemon.info eco[2321]: (gl-ngx-session:454) new ws
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:48:37:510] try to requestSetupDataCall 60 second later
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:49:37:572] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:49:37:572] call_end_reason is 1
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:49:37:572] call_end_reason_type is 2
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:49:37:573] call_end_reason_verbose is 210
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:49:37:573] try to requestSetupDataCall 60 second later
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:50:37:637] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:50:37:637] call_end_reason is 1
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:50:37:637] call_end_reason_type is 2
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:50:37:637] call_end_reason_verbose is 210
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:50:37:637] try to requestSetupDataCall 60 second later
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:51:37:703] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:51:37:703] call_end_reason is 1
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:51:37:703] call_end_reason_type is 2
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:51:37:703] call_end_reason_verbose is 210
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:51:37:704] try to requestSetupDataCall 60 second later
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:52:37:773] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Tue Apr 23 16:52:37 2024 daemon.notice netifd: modem_0001 (27957): [04-23_16:52:37:773] call_end_reason is 1
Tue Apr 23 16:52:37 2024 daemon.info eco[2321]: (gl-ngx-session:459) del ws
Tue Apr 23 16:52:38 2024 daemon.info eco[2321]: (gl-ngx-session:454) new ws

On my device it works out of the box. Have you tried to flash the device with the latest firmware version without keeping the old settings ?

BTW, to which phone number are you trying to send ? Same isp or different ?

Can you share your sms send screenshot before hitting the send please?

hello

Can you refer to this post to try something out?