|
|
| SMS Server Tools 3 Community |
| Welcome, Guest. The forum is currently read-only, but will open soon. |
Sat Aug 23, 2025 22:01 |
Page: 1
| Keywords: Mode: All keywords (AND) |
|
Sat Jan 21, 2023 01:20
|
Masterlog80: Working with no issues for weeks!
Thank you for your assistance @keke, very appreciated
|
|
Sun Dec 25, 2022 01:37
|
Masterlog80: I think I have found the root cause.
Testing a workaround now.
|
|
Sun Dec 25, 2022 00:22
|
Masterlog80:
That is, when you reboot the system, smsd works for some time without any problems. Later a message is received and then the problems begin.
Your event handler says: "Restarting SMSd service". Whatever is going on there, take it out. There is no need to restart smsd from within the script, nor should you do so.
Smsd should regularly check if there are any extra processes running, and stop if necessary. I don't know why it doesn't work in your case. Anyway, forget about stopping processes with cron, just remove starting new processes.
Well, the "Restarting SMSd service" is just the output of an echo I put in the event handler to eventually restart SMSd but I didn't put any command after so it's just a message.
Here is what is going on after some hours:
root@gsm-siemens:/var/log/smstools# ps aux | grep smsd
smsd 29 4.0 0.0 18272 5096 ? S 01:01 19:43 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 388 4.6 0.0 18268 5068 ? S 03:02 17:17 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 759 5.8 0.0 18268 5156 ? S 05:02 14:50 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 1255 5.6 0.0 18272 5100 ? S 07:03 7:28 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 1625 0.0 0.0 18232 4884 ? Ss 09:03 0:00 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 1626 4.5 0.0 18272 5096 ? R 09:03 0:31 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
root 1752 0.0 0.0 12864 908 pts/0 S+ 09:14 0:00 grep smsd
root@gsm-siemens:/var/log/smstools#
root@gsm-siemens:/var/log/smstools# cat smsd.log | grep started.
2022-12-24 18:21:04,2, smsd: Smsd v3.1.15 started.
2022-12-24 18:21:04,5, smsd: Outgoing file checker has started. PID: 10085.
2022-12-24 18:21:04,5, GSM0: Modem handler 0 has started. PID: 10086.
2022-12-24 20:21:29,2, smsd: Smsd v3.1.15 started.
2022-12-24 20:21:29,5, smsd: Outgoing file checker has started. PID: 10451.
2022-12-24 20:21:29,5, GSM0: Modem handler 0 has started. PID: 10452.
2022-12-24 22:21:55,2, smsd: Smsd v3.1.15 started.
2022-12-24 22:21:55,5, smsd: Outgoing file checker has started. PID: 10822.
2022-12-24 22:21:55,5, GSM0: Modem handler 0 has started. PID: 10823.
2022-12-25 00:22:21,2, smsd: Smsd v3.1.15 started.
2022-12-25 00:22:21,5, smsd: Outgoing file checker has started. PID: 11194.
2022-12-25 00:22:21,5, GSM0: Modem handler 0 has started. PID: 11195.
2022-12-25 01:01:46,2, smsd: Smsd v3.1.15 started.
2022-12-25 01:01:46,5, smsd: Outgoing file checker has started. PID: 28.
2022-12-25 01:01:46,5, GSM0: Modem handler 0 has started. PID: 29.
2022-12-25 03:02:11,2, smsd: Smsd v3.1.15 started.
2022-12-25 03:02:11,5, smsd: Outgoing file checker has started. PID: 387.
2022-12-25 03:02:11,5, GSM0: Modem handler 0 has started. PID: 388.
2022-12-25 05:02:37,2, smsd: Smsd v3.1.15 started.
2022-12-25 05:02:37,5, smsd: Outgoing file checker has started. PID: 758.
2022-12-25 05:02:37,5, GSM0: Modem handler 0 has started. PID: 759.
2022-12-25 07:03:03,2, smsd: Smsd v3.1.15 started.
2022-12-25 07:03:03,5, smsd: Outgoing file checker has started. PID: 1254.
2022-12-25 07:03:03,5, GSM0: Modem handler 0 has started. PID: 1255.
2022-12-25 09:03:29,2, smsd: Smsd v3.1.15 started.
2022-12-25 09:03:29,5, smsd: Outgoing file checker has started. PID: 1625.
2022-12-25 09:03:29,5, GSM0: Modem handler 0 has started. PID: 1626.
root@gsm-siemens:/var/log/smstools#
root@gsm-siemens:/var/log/smstools# cat smsd.log | grep started. -A 1 -B 3
2022-12-24 18:21:04,2, smsd: Smsd v3.1.15 started.
2022-12-24 18:21:04,2, smsd: Running as smsd:dialout.
2022-12-24 18:21:04,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.kkKWZe /tmp/smsd_data.T37Cpf
2022-12-24 18:21:04,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2022-12-24 18:21:04,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2022-12-24 18:21:04,5, smsd: Outgoing file checker has started. PID: 10085.
2022-12-24 18:21:04,7, smsd: All PID's: 10085,10086
2022-12-24 18:21:04,5, GSM0: Modem handler 0 has started. PID: 10086.
2022-12-24 18:21:04,5, GSM0: Using check_memory_method 1: CPMS is used.
--
2022-12-24 20:21:24,7, GSM0: <- +CPMS: "SM",0,20,"SM",0,20,"SM",0,20 OK
2022-12-24 20:21:24,6, GSM0: Used memory is 0 of 20
2022-12-24 20:21:24,6, GSM0: No SMS received
2022-12-24 20:21:29,2, smsd: Smsd v3.1.15 started.
2022-12-24 20:21:29,2, smsd: Running as smsd:dialout.
2022-12-24 20:21:29,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.7jwumK /tmp/smsd_data.YmovXL
2022-12-24 20:21:29,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2022-12-24 20:21:29,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2022-12-24 20:21:29,5, smsd: Outgoing file checker has started. PID: 10451.
2022-12-24 20:21:29,7, smsd: All PID's: 10451,10452
2022-12-24 20:21:29,5, GSM0: Modem handler 0 has started. PID: 10452.
2022-12-24 20:21:29,5, GSM0: Using check_memory_method 1: CPMS is used.
--
Very strange.... :|
Regards,
|
|
Sat Dec 24, 2022 09:05
|
Masterlog80: Hello @keke,
Thank you for your support.
Indeed, you are correct, I have checked and there were multiple smsd services running.
Checking the logs, it seems that smsd it's getting automatic started every 2hours:
root@gsm-siemens:/var/log/smstools# cat smsd.log | grep start
2022-12-23 15:56:44,2, smsd: Smsd v3.1.15 started.
2022-12-23 15:56:53,3, GSM0: ! Input from SMSd received, starting the script to check the status is RECEIVED
2022-12-23 15:56:53,3, GSM0: ! SMS is RECEIVED, starting the script, setting the variables
2022-12-23 15:56:53,3, GSM0: ! Restarting SMSd service
2022-12-23 17:57:09,2, smsd: Smsd v3.1.15 started.
2022-12-23 19:57:35,2, smsd: Smsd v3.1.15 started.
2022-12-23 21:58:00,2, smsd: Smsd v3.1.15 started.
2022-12-23 23:58:26,2, smsd: Smsd v3.1.15 started.
2022-12-24 01:01:50,2, smsd: Smsd v3.1.15 started.
2022-12-24 03:02:14,2, smsd: Smsd v3.1.15 started.
2022-12-24 05:02:40,2, smsd: Smsd v3.1.15 started.
2022-12-24 07:03:06,2, smsd: Smsd v3.1.15 started.
2022-12-24 09:03:32,2, smsd: Smsd v3.1.15 started.
2022-12-24 11:03:58,2, smsd: Smsd v3.1.15 started.
2022-12-24 13:04:24,2, smsd: Smsd v3.1.15 started.
2022-12-24 15:04:50,2, smsd: Smsd v3.1.15 started.
2022-12-24 17:05:16,2, smsd: Smsd v3.1.15 started.
I don't really know why this happens (there is nothing on cron, etc.), but the behaviour is regular, so it's very suspicious. I am proceeding to recreate the container and raising loglevel to see if the logs can explain why this happens.
I think I can temporary fix it by setting a cron job to stop the service and kill all the PID of smsd by executing every 1h or less, but it would be tricky.
Again, any suggestions are more than welcome!
Regards,
|
|
Fri Dec 23, 2022 06:53
|
Masterlog80: Hello guys,
After 1 day, it seems there is an issue.
Specifically the device seems stuck to "Receiving" mode, but it doesn't receive any SMS.
Here are some detail:
root@gsm-siemens:/var/log/smstools/smsd_stats# cat status
Status: 22-12-23 15:45:07, r---------------------------------------------------------------
GSM0: 22-12-23 15:45:00, Receiving, 0, 0, 0
root@gsm-siemens:/var/log/smstools/smsd_stats# date
Fri Dec 23 15:48:02 JST 2022
root@gsm-siemens:/var/log/smstools/smsd_stats#
And also the log file:
root@gsm-siemens:/var/log/smstools# tail smsd.log -n 60
2022-12-23 15:47:55,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:47:55,7, GSM0: -> AT+CSQ
2022-12-23 15:47:55,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:47:59,7, GSM0: put_command expected (\+CPMS:.*OK)|(ERROR), timeout occurred. 1.
2022-12-23 15:47:59,7, GSM0: <- +CREG: 2,5, 2A3F, 0 OK
2022-12-23 15:47:59,6, GSM0: Command failed.
2022-12-23 15:47:59,6, GSM0: No SMS received (reading interrupted)
2022-12-23 15:48:00,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 3.
2022-12-23 15:48:00,7, GSM0: <-
2022-12-23 15:48:00,7, GSM0: -> AT
2022-12-23 15:48:00,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:00,7, GSM0: put_command expected (\+CREG:.*OK)|(ERROR), timeout occurred. 2.
2022-12-23 15:48:00,7, GSM0: <-
2022-12-23 15:48:00,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-12-23 15:48:01,7, GSM0: -> AT+CSQ
2022-12-23 15:48:01,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:02,6, GSM0: Checking device for incoming SMS
2022-12-23 15:48:02,6, GSM0: Checking if modem is ready
2022-12-23 15:48:02,7, GSM0: -> AT
2022-12-23 15:48:02,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:02,7, GSM0: <- OK
2022-12-23 15:48:03,7, GSM0: -> AT+CREG?
2022-12-23 15:48:03,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:03,7, GSM0: <- +CSQ: 16,99 OK OK +CSQ: 16,99 OK +CREG: 2,5, 2A3F, 0 OK
2022-12-23 15:48:03,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-12-23 15:48:03,7, GSM0: put_command expected (\+CREG:.*OK)|(ERROR), timeout occurred. 3.
2022-12-23 15:48:03,7, GSM0: <-
2022-12-23 15:48:03,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-12-23 15:48:04,7, GSM0: -> AT+CSQ
2022-12-23 15:48:04,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:04,7, GSM0: -> AT+CSQ
2022-12-23 15:48:04,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:04,7, GSM0: <- +CSQ: 16,99 OK
2022-12-23 15:48:04,6, GSM0: Pre-initializing modem
2022-12-23 15:48:04,7, GSM0: <- +CSQ: 16,99 OK
2022-12-23 15:48:04,5, GSM0: Signal Strength Indicator: (16,99) -81 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-23 15:48:04,7, GSM0: -> ATE0+CMEE=1;+CREG=2
2022-12-23 15:48:04,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:05,7, GSM0: -> AT+CREG?
2022-12-23 15:48:05,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:05,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 4.
2022-12-23 15:48:05,7, GSM0: <-
2022-12-23 15:48:05,7, GSM0: <- +CREG: 2,5, 2A3F, 0 OK
2022-12-23 15:48:05,6, GSM0: Initializing modem
2022-12-23 15:48:05,7, GSM0: ->
2022-12-23 15:48:05,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:05,7, GSM0: -> AT+CPMS="SM","SM","SM"
2022-12-23 15:48:05,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:05,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 4.
2022-12-23 15:48:05,7, GSM0: <-
2022-12-23 15:48:06,7, GSM0: -> AT+CREG?
2022-12-23 15:48:06,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:06,7, GSM0: <- +CREG: 2,5, 2A3F, 0 OK
2022-12-23 15:48:06,6, GSM0: Modem is registered to a roaming partner network
2022-12-23 15:48:06,6, GSM0: Selecting PDU mode
2022-12-23 15:48:06,7, GSM0: -> AT+CMGF=0
2022-12-23 15:48:06,7, GSM0: Command is sent, waiting for the answer
2022-12-23 15:48:06,7, GSM0: <- OK
2022-12-23 15:48:06,7, GSM0: -> AT+CSQ
2022-12-23 15:48:06,7, GSM0: Command is sent, waiting for the answer
root@gsm-siemens:/var/log/smstools# date
Fri Dec 23 15:48:16 JST 2022
root@gsm-siemens:/var/log/smstools#
I had a similar issue with an Huawei E176 device. I suspected being related to the power on the USB, but I have noticed it on multiple servers (with and without Docker), and also using a powered USB Hub.
Restarting the service doesn't help always, as an HW reboot can fix it on most cases.
Any suggestions?
Regards,
|
|
Thu Dec 22, 2022 08:51
|
Masterlog80: Nevermind, I have set memory_start = 0 to the correct section and I am monitoring the status.
Thanks again, @keke!
|
|
Tue Dec 20, 2022 04:23
|
|
|
|
Tue Dec 20, 2022 03:55
|
|
|
|
Tue Dec 20, 2022 00:37
|
Masterlog80:
Do NOT use vwdial style initialization because it sets the modem to data mode. Use AT+CPMS="SM","SM","SM". Make sure the modem is reset before trying to read the messages.
If you still have problems, show the report_device_details output too.
Hello @keke, thank you for your assistance.
Despite there are some few errors on the logs:
2022-12-20 00:33:14,6, GSM0: Trying to get stored message 19
2022-12-20 00:33:14,7, GSM0: -> AT+CMGR=19
2022-12-20 00:33:14,7, GSM0: Command is sent, waiting for the answer
2022-12-20 00:33:14,7, GSM0: <- OK
2022-12-20 00:33:14,6, GSM0: Trying to get stored message 20
2022-12-20 00:33:15,7, GSM0: -> AT+CMGR=20
2022-12-20 00:33:15,7, GSM0: Command is sent, waiting for the answer
2022-12-20 00:33:15,7, GSM0: <- +CMS ERROR: 321 (Invalid memory index)
2022-12-20 00:33:15,6, GSM0: Checking device for incoming SMS
2022-12-20 00:33:15,6, GSM0: Checking memory size
2022-12-20 00:33:15,7, GSM0: -> AT+CPMS?
2022-12-20 00:33:15,7, GSM0: Command is sent, waiting for the answer
2022-12-20 00:33:15,7, GSM0: <- +CPMS: "SM",1,20,"SM",1,20,"SM",1,20 OK
2022-12-20 00:33:15,6, GSM0: Used memory is 1 of 20
2022-12-20 00:33:15,6, GSM0: Trying to get stored message 1
It seems working with the new initialization string!
2022-12-20 00:33:01,6, GSM0: Trying to get stored message 1
2022-12-20 00:33:02,7, GSM0: -> AT+CMGR=1
2022-12-20 00:33:02,7, GSM0: Command is sent, waiting for the answer
2022-12-20 00:33:02,7, GSM0: <- +CMGR: 0,,56 099143060780160060F6040BD0C7F7FBCC2E030000222102102355402AC7966D0683D970A0F41C947FD7E5A0E3FB7D669741$
2022-12-20 00:33:02,5, GSM0: SMS received, From: Google
2022-12-20 00:33:02,6, GSM0: Wrote an incoming message file: /var/spool/sms/incoming/GSM0.WxZ7sN
2022-12-20 00:33:02,7, GSM0: Running eventhandler: /docker_script/scripts/forwardsms.sh RECEIVED /var/spool/sms/incoming/GSM0.WxZ7sN
2022-12-20 00:33:05,7, GSM0: Done: eventhandler, execution time 3 sec., status: 0 (0)
2022-12-20 00:33:05,3, GSM0: Exec: eventhandler said something:
2022-12-20 00:33:05,3, GSM0: ! Input from SMSd received, starting the script to check the status is RECEIVED
....
2022-12-20 00:33:05,3, GSM0: ! Script completed
2022-12-20 00:33:05,6, GSM0: Deleting message 1
2022-12-20 00:33:05,7, GSM0: -> AT+CMGD=1
I will keep monitoring for the next days, just in case.
Regards,
|
|
Mon Dec 19, 2022 08:40
|
Masterlog80: Sorry for the additional update. After recreating the container (ideally with a newer Linux image) all the errors seems to be solved as below:
root@gsm-siemens:/var/log/smstools# cat smsd.log
2022-12-19 08:17:01,2, smsd: Smsd v3.1.15 started.
2022-12-19 08:17:01,2, smsd: Running as smsd:dialout.
2022-12-19 08:17:01,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.ZuSK8E /tmp/smsd_data.NM7994
2022-12-19 08:17:01,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2022-12-19 08:17:01,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2022-12-19 08:17:01,5, smsd: Outgoing file checker has started. PID: 10084.
2022-12-19 08:17:01,7, smsd: All PID's: 10084,10085
2022-12-19 08:17:01,5, GSM0: Modem handler 0 has started. PID: 10085.
2022-12-19 08:17:01,5, GSM0: Using check_memory_method 1: CPMS is used.
2022-12-19 08:17:01,6, GSM0: Checking device for incoming SMS
2022-12-19 08:17:01,6, GSM0: Checking if modem is ready
2022-12-19 08:17:01,7, GSM0: -> AT
2022-12-19 08:17:01,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:17:02,7, GSM0: <- AT OK
2022-12-19 08:17:02,6, GSM0: Pre-initializing modem
2022-12-19 08:17:02,7, GSM0: -> ATE0+CMEE=1;+CREG=2
2022-12-19 08:17:02,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:17:02,7, GSM0: <- ATE0+CMEE=1;+CREG=2 OK
2022-12-19 08:17:02,7, GSM0: -> AT+CSQ
2022-12-19 08:17:02,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:17:03,7, GSM0: <- +CSQ: 19,99 OK
2022-12-19 08:17:03,6, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-19 08:17:03,6, GSM0: Checking if Modem is registered to the network
2022-12-19 08:17:03,7, GSM0: -> AT+CREG?
....
2022-12-19 08:20:43,6, GSM0: Used memory is 0 of 11
2022-12-19 08:20:43,6, GSM0: No SMS received
2022-12-19 08:20:53,6, GSM0: Checking device for incoming SMS
2022-12-19 08:20:53,6, GSM0: Checking if modem is ready
2022-12-19 08:20:53,7, GSM0: -> AT
2022-12-19 08:20:53,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:53,7, GSM0: <- OK
2022-12-19 08:20:53,6, GSM0: Pre-initializing modem
2022-12-19 08:20:54,7, GSM0: -> ATE0+CMEE=1;+CREG=2
2022-12-19 08:20:54,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:54,7, GSM0: <- OK
2022-12-19 08:20:54,7, GSM0: -> AT+CSQ
2022-12-19 08:20:54,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:54,7, GSM0: <- +CSQ: 19,99 OK
2022-12-19 08:20:54,6, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-19 08:20:54,6, GSM0: Checking if Modem is registered to the network
2022-12-19 08:20:55,7, GSM0: -> AT+CREG?
2022-12-19 08:20:55,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:55,7, GSM0: <- +CREG: 2,5, 2A3F, 0 OK
2022-12-19 08:20:55,6, GSM0: Modem is registered to a roaming partner network
2022-12-19 08:20:55,6, GSM0: Selecting PDU mode
2022-12-19 08:20:55,7, GSM0: -> AT+CMGF=0
2022-12-19 08:20:55,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:55,7, GSM0: <- OK
2022-12-19 08:20:55,6, GSM0: Changing SMSC
2022-12-19 08:20:56,7, GSM0: -> AT+CSCA="+393457892729"
2022-12-19 08:20:56,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:56,7, GSM0: <- OK
2022-12-19 08:20:56,6, GSM0: Checking memory size
2022-12-19 08:20:56,7, GSM0: -> AT+CPMS?
2022-12-19 08:20:56,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:20:56,7, GSM0: <- +CPMS: "ME",0,11,"ME",0,11,"ME",0,11 OK
2022-12-19 08:20:56,6, GSM0: Used memory is 0 of 11
2022-12-19 08:20:56,6, GSM0: No SMS received
root@gsm-siemens:/var/log/smstools#
root@gsm-siemens:/var/log/smstools# ps aux | grep sms
smsd 10084 0.0 0.0 18232 4864 ? Ss 17:17 0:00 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 10085 1.8 0.0 18268 5008 ? S 17:17 0:05 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
root 10146 0.0 0.0 12864 948 pts/0 S+ 17:22 0:00 grep sms
root@gsm-siemens:/var/log/smstools#
root@gsm-siemens:/var/log/smstools# date
Mon Dec 19 17:22:31 JST 2022
root@gsm-siemens:/var/log/smstools#
root@gsm-siemens:/var/log/smstools/smsd_stats# cat status
Status: 22-12-19 08:23:21, i---------------------------------------------------------------
GSM0: 22-12-19 08:23:08, Idle, 0, 0, 0, ssi: -75 dBm (Good), ber: ??
root@gsm-siemens:/var/log/smstools/smsd_stats#
root@gsm-siemens:/var/log/smstools/smsd_stats# cat GSM0.counter
GSM0: 0
root@gsm-siemens:/var/log/smstools/smsd_stats#
The issue now is that it doesn't receive receive (or process) any SMS that I have sent to the SIM card but there are no useful messages to troubleshoot the reason.
Then, adding the initialization strings (obtained by vwdial) to /etc/smsd.conf strings cause another issue:
root@gsm-siemens:/var/log/smstools# cat smsd.log
2022-12-19 08:26:49,2, smsd: Smsd v3.1.15 started.
2022-12-19 08:26:49,2, smsd: Running as smsd:dialout.
2022-12-19 08:26:49,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.50c9p9 /tmp/smsd_data.1KIGBT
2022-12-19 08:26:49,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2022-12-19 08:26:49,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2022-12-19 08:26:49,5, smsd: Outgoing file checker has started. PID: 10084.
2022-12-19 08:26:49,7, smsd: All PID's: 10084,10085
2022-12-19 08:26:49,5, GSM0: Modem handler 0 has started. PID: 10085.
2022-12-19 08:26:49,5, GSM0: Using check_memory_method 1: CPMS is used.
2022-12-19 08:26:49,6, GSM0: Checking device for incoming SMS
2022-12-19 08:26:49,6, GSM0: Checking if modem is ready
2022-12-19 08:26:50,7, GSM0: -> AT
2022-12-19 08:26:50,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:26:50,7, GSM0: <- OK
2022-12-19 08:26:50,6, GSM0: Pre-initializing modem
2022-12-19 08:26:50,7, GSM0: -> ATE0+CMEE=1;+CREG=2
2022-12-19 08:26:50,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:26:50,7, GSM0: <- OK
2022-12-19 08:26:50,6, GSM0: Initializing modem
2022-12-19 08:26:51,7, GSM0: -> ATZ
2022-12-19 08:26:51,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:26:51,7, GSM0: <- OK
2022-12-19 08:26:51,7, GSM0: -> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
2022-12-19 08:26:51,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:26:51,7, GSM0: <- OK
2022-12-19 08:26:52,7, GSM0: -> AT+CSQ
2022-12-19 08:26:52,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:26:52,7, GSM0: <- AT+CSQ +CSQ: 19,99 OK
2022-12-19 08:26:52,6, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-19 08:26:52,6, GSM0: Checking if Modem is registered to the network
2022-12-19 08:26:52,7, GSM0: -> AT+CREG?
2022-12-19 08:26:52,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:26:52,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-12-19 08:26:52,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 1. TIME
....
2022-12-19 08:35:18,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 42. TIME
2022-12-19 08:35:19,7, GSM0: -> AT+CSQ
2022-12-19 08:35:19,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:35:20,7, GSM0: <- AT+CSQ +CSQ: 19,99 OK
2022-12-19 08:35:20,5, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-19 08:35:20,7, GSM0: -> AT+CREG?
2022-12-19 08:35:20,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:35:20,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-12-19 08:35:20,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 43. TIME
2022-12-19 08:35:21,7, GSM0: -> AT+CSQ
2022-12-19 08:35:21,7, GSM0: Command is sent, waiting for the answer
2022-12-19 08:35:22,7, GSM0: <- AT+CSQ +CSQ: 19,99 OK
2022-12-19 08:35:22,5, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
root@gsm-siemens:/var/log/smstools#
root@gsm-siemens:/var/log/smstools# ps aux | grep sms
smsd 10084 0.0 0.0 18232 4948 ? Ss 17:26 0:00 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 10085 3.4 0.0 18268 5084 ? S 17:26 0:21 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
root 10150 0.0 0.0 12864 904 pts/0 S+ 17:37 0:00 grep sms
root@gsm-siemens:/var/log/smstools#
Regards,
|
|
Mon Dec 19, 2022 07:31
|
Masterlog80: Other information:
root@gsm-siemens:/var/log/smstools# ps aux | grep smsd
smsd 355 0.0 0.0 18232 4964 ? Ss 16:26 0:00 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
smsd 356 3.5 0.0 18268 5104 ? S 16:26 0:07 /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working -usmsd -gdialout
root 364 0.0 0.0 12864 972 pts/0 S+ 16:29 0:00 grep smsd
root@gsm-siemens:/var/log/smstools#
Regards,
|
|
Mon Dec 19, 2022 07:28
|
Masterlog80: Just posting the last content of smsd.log here:
2022-12-19 07:16:29,7, GSM0: -> AT+CREG?
2022-12-19 07:16:29,7, GSM0: Command is sent, waiting for the answer
2022-12-19 07:16:29,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-12-19 07:16:29,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 2. TIME
2022-12-19 07:16:30,7, GSM0: -> AT+CSQ
2022-12-19 07:16:30,7, GSM0: Command is sent, waiting for the answer
2022-12-19 07:16:31,7, GSM0: <- AT+CSQ +CSQ: 19,99 OK
2022-12-19 07:16:31,5, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-19 07:16:31,7, GSM0: -> AT+CREG?
2022-12-19 07:16:31,7, GSM0: Command is sent, waiting for the answer
2022-12-19 07:16:31,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-12-19 07:16:31,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 3. TIME
2022-12-19 07:16:32,7, GSM0: -> AT+CSQ
2022-12-19 07:16:32,7, GSM0: Command is sent, waiting for the answer
2022-12-19 07:16:33,7, GSM0: <- AT+CSQ +CSQ: 19,99 OK
2022-12-19 07:16:33,5, GSM0: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable
2022-12-19 07:16:33,7, GSM0: -> AT+CREG?
2022-12-19 07:16:33,7, GSM0: Command is sent, waiting for the answer
2022-12-19 07:16:33,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-12-19 07:16:33,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 4. TIME
2022-12-19 07:16:34,7, GSM0: -> AT+CSQ
2022-12-19 07:16:34,7, GSM0: Command is sent, waiting for the answer
If I run the same commands on smsd -C GSM0 I get similar results as below:
root@gsm-siemens:/var/log/smstools# service smstools stop
Stopping SMS Daemon: smsd not running.
root@gsm-siemens:/var/log/smstools# smsd -C GSM0
Communicating with GSM0. ( Press Ctrl-C to abort. )
( If you need to send Ctrl-Z, change the suspend character first, like stty susp \^N )
Default device is /dev/ttyUSB1
Press Enter to start or type an another device name.
Opening device /dev/ttyUSB1
Ready.
AT+CREG?
+CREG: 0,5
OK
AT+CSQ
+CSQ: 19,99
OK
AT+CREG?
+CREG: 0,5
OK
AT+CSQ
+CSQ: 19,99
OK
I will appreciate any suggestions here!
Regards,
|
|
Mon Dec 19, 2022 07:14
|
Masterlog80:
.....
It strongly seems that the modem is shared by too many processes, or Docker is somehow messing up the communication. All I can do is ask you to do a new test after you have made sure that the modem is not used by any other process (for example, another smsd).
You can also test the modem with the smsd communication feature. First kill all smsd processes and make sure they are killed. Then start smsd with smsd -C GSM0 and send an AT command to the modem. The answer should be OK and nothing else. Then wait with your hands in the air. If the modem reports various things even though they have not been asked in this terminal, it should be clear that there is some other process that is asking them somewhere.
Hello @keke,
First of all, thank you for your assistance. I have just proceeded as you have suggested, and here is the result:
root@gsm-siemens:/docker_script# smsd -C GSM0
Communicating with GSM0. ( Press Ctrl-C to abort. )
( If you need to send Ctrl-Z, change the suspend character first, like stty susp \^N )
Default device is /dev/ttyUSB1
Press Enter to start or type an another device name.
Opening device /dev/ttyUSB1
Ready.
AT+CGMM
HSDPA Modem
OK
AT+CGMR
M7227-1.1 1 [Aug 17 2011 05:00:00]
OK
AT+CGSN
351602000025260
OK
After some minutes, no new lines have been added to the output, so I am assuming that no other process(es) are actually using the device.
Then, I have seen another post for the same device (with no updates) here:
http://smstools3.kekekasvi.com/topic.php?id=1620
At the issue is still ongoing, if there are no idea/suggestions for this, I am wondering to buy another modem but of course I'd prefer to keep this one if someone cal help!
Regards,
|
|
Tue Dec 13, 2022 13:08
|
|
|
|
Thu Nov 17, 2022 23:25
|
Masterlog80:
Please stop wvdial and any other processes that may be using the modem. Smstools must be the one and only process which uses the modem.
Hello @keke, thank you for your update.
Well, I had installed "wvdial" only for the purpose of getting the values for "init", and as now the system is running in a Docker container it's basically just "smstools" and the OS :D :-)
Also it works with an HUAWEI E176 USB dongle, but as the device has some issue I am trying to switch to this new one.
Any help or suggestions will be very appreciated!
|
|
Tue Nov 15, 2022 01:15
|
Masterlog80: Hello,
I have created the new topic http://smstools3.kekekasvi.com/topic.php?id=1647 for a similar issue, so if you have may found a solution I'd appreciate assistance while I keep investigating on my side.
Regards,
|
|
Mon Nov 14, 2022 10:24
|
|
|
|
Mon Nov 14, 2022 10:04
|
Masterlog80: Operating system name and version: Debian GNU/Linux 9 (stretch) (on Docker)
Version of smsd: Debian GNU/Linux 9 (stretch)
Smsd installed from: package repository
Name and model of a modem / phone: Siemens SG75
Interface: USB
Checking the led, the device seems connected to the Network, but from Linux it's unable to receive and process any SMS.
Putting the dongle on Windows, it's definitely fine.
Here is my config (the most relevant settings):
devices = GSM0
loglevel = 7
status_interval = 10
stats_interval = 3600
receive_before_send = no
autosplit = 3
[GSM0]
device = /dev/ttyUSB0
incoming = yes
smsc = +393492000200
baudrate = 9600
pin = ignore
report_device_details = yes
The "smsc" value has been taken from official Vodafone Italy documentation.
Here is smsd.log:
2022-11-14 09:40:44,2, smsd: Smsd v3.1.15 started.
2022-11-14 09:40:44,2, smsd: Running as smsd:dialout.
2022-11-14 09:40:44,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.2YRIGS /tmp/smsd_data.LjtAIF
2022-11-14 09:40:44,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2022-11-14 09:40:44,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2022-11-14 09:40:44,5, smsd: Outgoing file checker has started. PID: 16285.
2022-11-14 09:40:44,7, smsd: All PID's: 16285,16286
2022-11-14 09:40:44,5, GSM0: Modem handler 0 has started. PID: 16286.
2022-11-14 09:40:44,5, GSM0: Using check_memory_method 1: CPMS is used.
2022-11-14 09:40:44,6, GSM0: Checking device for incoming SMS
2022-11-14 09:40:44,6, GSM0: Checking if modem is ready
2022-11-14 09:40:44,7, GSM0: -> AT
2022-11-14 09:40:44,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:40:45,7, GSM0: <- 351602000025260 OK
2022-11-14 09:40:45,6, GSM0: Pre-initializing modem
2022-11-14 09:40:45,7, GSM0: -> ATE0+CMEE=1;+CREG=2
2022-11-14 09:40:45,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:40:50,7, GSM0: <- +CSQ: 18,99 OK
2022-11-14 09:40:50,7, GSM0: -> AT+CSQ
2022-11-14 09:40:50,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:40:50,7, GSM0: <- +CPMS: "ME",0,11,"ME",0,11,"ME",0,11 OK
2022-11-14 09:40:50,6, GSM0: Checking if Modem is registered to the network
2022-11-14 09:40:51,7, GSM0: -> AT+CREG?
2022-11-14 09:40:51,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:41:00,7, GSM0: <- +CSQ: 18,99 OK +CREG: 2,5, 2A3F, 0 OK
2022-11-14 09:41:00,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:41:01,7, GSM0: -> AT+CSQ
2022-11-14 09:41:01,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:41:03,7, GSM0: <- OK
2022-11-14 09:41:03,7, GSM0: -> AT+CREG?
2022-11-14 09:41:03,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:41:14,7, GSM0: <- OK +CPMS: "ME",0,11,"ME",0,11,"ME",0,11 OK
2022-11-14 09:41:14,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:41:16,7, GSM0: -> AT+CSQ
2022-11-14 09:41:16,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:41:26,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 1.
2022-11-14 09:41:26,7, GSM0: <-
2022-11-14 09:41:26,7, GSM0: -> AT+CREG?
2022-11-14 09:41:26,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:41:45,7, GSM0: <- AT+CSQ +CSQ: 18,99 OK AT+CSQ +CSQ: 18,99 OK ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK AT OK AT+CREG? +CREG: 0,5 OK
2022-11-14 09:41:45,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:41:46,7, GSM0: -> AT+CSQ
2022-11-14 09:41:46,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:41:48,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-11-14 09:41:48,7, GSM0: -> AT+CREG?
2022-11-14 09:41:48,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:00,7, GSM0: <- OK +CSQ: 18,99 OK +CSQ: 18,99 OK +CREG: 0,5 OK
2022-11-14 09:42:00,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:42:01,7, GSM0: -> AT+CSQ
2022-11-14 09:42:01,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:05,7, GSM0: <- AT OK
2022-11-14 09:42:05,7, GSM0: -> AT+CREG?
2022-11-14 09:42:05,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:08,7, GSM0: <- +CREG: 0,5 OK
2022-11-14 09:42:08,6, GSM0: Modem is registered to a roaming partner network
2022-11-14 09:42:08,6, GSM0: Selecting PDU mode
2022-11-14 09:42:08,7, GSM0: -> AT+CMGF=0
2022-11-14 09:42:08,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:10,7, GSM0: <- +CSQ: 18,99 OK
2022-11-14 09:42:10,6, GSM0: Changing SMSC
2022-11-14 09:42:10,7, GSM0: -> AT+CSCA="+393492000200"
2022-11-14 09:42:10,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:11,7, GSM0: <- ATE0+CMEE=1 OK
2022-11-14 09:42:11,7, GSM0: -> AT+CIMI
2022-11-14 09:42:11,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:16,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 1.
2022-11-14 09:42:16,7, GSM0: <-
2022-11-14 09:42:16,7, GSM0: -> AT+CGSN
2022-11-14 09:42:16,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:19,7, GSM0: <- +CSQ: 18,99 OK
2022-11-14 09:42:19,5, GSM0: CGSN: 18,99
2022-11-14 09:42:19,5, GSM0: IMSI:
2022-11-14 09:42:19,6, GSM0: Checking if reading of messages is supported
2022-11-14 09:42:19,7, GSM0: -> AT+CPMS?
2022-11-14 09:42:19,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:42:20,7, GSM0: <- +CREG: 0,5 OK
2022-11-14 09:42:20,7, GSM0: ## Start of device details
022-11-14 09:42:20,7, GSM0: # Manufacturer identification:
2022-11-14 09:42:20,7, GSM0: -> AT+CGMI
2022-11-14 09:42:20,7, GSM0: <- +CREG: 0,5
OK
2022-11-14 09:42:20,7, GSM0: # Model identification:
2022-11-14 09:42:21,7, GSM0: -> AT+CGMM
2022-11-14 09:42:26,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 1.
2022-11-14 09:42:26,7, GSM0: <-
2022-11-14 09:42:26,7, GSM0: # Revision identification:
2022-11-14 09:42:26,7, GSM0: -> AT+CGMR
2022-11-14 09:42:29,7, GSM0: <- +CREG: 0,5
OK
2022-11-14 09:42:29,7, GSM0: # New message indications, list of supported modes:
...
I have also installed and run "wvdial", ran it and added the following lines to smsd.conf:
init = ATZ
init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
But the result didn't change, here is the new smsd.log:
2022-11-14 09:53:28,2, smsd: Smsd v3.1.15 started.
2022-11-14 09:53:28,2, smsd: Running as smsd:dialout.
2022-11-14 09:53:28,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.qIBhxv /tmp/smsd_data.gXBPgq
2022-11-14 09:53:28,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0)
2022-11-14 09:53:28,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2022-11-14 09:53:28,5, smsd: Outgoing file checker has started. PID: 18026.
2022-11-14 09:53:28,7, smsd: All PID's: 18026,18027
2022-11-14 09:53:28,5, GSM0: Modem handler 0 has started. PID: 18027.
2022-11-14 09:53:28,5, GSM0: Using check_memory_method 1: CPMS is used.
2022-11-14 09:53:28,6, GSM0: Checking device for incoming SMS
2022-11-14 09:53:28,6, GSM0: Checking if modem is ready
2022-11-14 09:53:28,7, GSM0: -> AT
2022-11-14 09:53:28,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:30,7, GSM0: <- OK
2022-11-14 09:53:30,6, GSM0: Pre-initializing modem
2022-11-14 09:53:30,7, GSM0: -> ATE0+CMEE=1;+CREG=2
2022-11-14 09:53:30,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:30,7, GSM0: <- +CSQ: 18,99 OK
2022-11-14 09:53:30,6, GSM0: Initializing modem
2022-11-14 09:53:31,7, GSM0: -> ATZ
2022-11-14 09:53:31,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:32,7, GSM0: <- +CREG: 0,5 OK
2022-11-14 09:53:32,7, GSM0: -> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
2022-11-14 09:53:32,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:42,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 1.
2022-11-14 09:53:42,7, GSM0: <-
2022-11-14 09:53:42,7, GSM0: -> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
2022-11-14 09:53:42,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:44,7, GSM0: <- +CSQ: 18,99 OK
2022-11-14 09:53:44,6, GSM0: Signal Strength Indicator: (18,99) -77 dBm (Good), Bit Error Rate: not known or not detectable
2022-11-14 09:53:44,7, GSM0: -> AT+CSQ
2022-11-14 09:53:44,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:46,7, GSM0: <- +CREG: 0,5 OK
2022-11-14 09:53:46,6, GSM0: Checking if Modem is registered to the network
2022-11-14 09:53:47,7, GSM0: -> AT+CREG?
2022-11-14 09:53:47,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:53:57,7, GSM0: <- +CSQ: 18,99 OK +CREG: 0,5 OK
2022-11-14 09:53:57,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:53:58,7, GSM0: -> AT+CSQ
2022-11-14 09:53:58,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:01,7, GSM0: <- OK
2022-11-14 09:54:02,7, GSM0: -> AT+CREG?
2022-11-14 09:54:02,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:06,7, GSM0: <- +CPMS: "ME",0,11,"ME",0,11,"ME",0,11 OK
2022-11-14 09:54:06,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:54:07,7, GSM0: -> AT+CSQ
2022-11-14 09:54:07,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:17,7, GSM0: put_command expected (OK)|(ERROR), timeout occurred. 1.
2022-11-14 09:54:17,7, GSM0: <-
2022-11-14 09:54:17,7, GSM0: -> AT+CREG?
2022-11-14 09:54:17,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:27,7, GSM0: put_command expected (\+CREG:.*OK)|(ERROR), timeout occurred. 2.
2022-11-14 09:54:27,7, GSM0: <-
2022-11-14 09:54:27,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:54:28,7, GSM0: -> AT+CSQ
2022-11-14 09:54:28,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:34,7, GSM0: <- AT+CSQ +CSQ: 18,99 OK
2022-11-14 09:54:34,5, GSM0: Signal Strength Indicator: (18,99) -77 dBm (Good), Bit Error Rate: not known or not detectable
2022-11-14 09:54:34,7, GSM0: -> AT+CREG?
2022-11-14 09:54:34,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:35,7, GSM0: <- AT+CREG? +CREG: 0,5 OK
2022-11-14 09:54:35,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 4. TIME
2022-11-14 09:54:36,7, GSM0: -> AT+CSQ
2022-11-14 09:54:36,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:37,7, GSM0: <- OK
2022-11-14 09:54:37,7, GSM0: -> AT+CREG?
2022-11-14 09:54:37,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:46,7, GSM0: <- AT OK ATE0+CMEE=1;+CREG=2 OK +CSQ: 18,99 OK +CREG: 2,5, 2A3F, 0 OK
2022-11-14 09:54:46,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:54:47,7, GSM0: -> AT+CSQ
2022-11-14 09:54:47,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:54:57,7, GSM0: <- +CREG: 2,5, 2A3F, 0 OK
2022-11-14 09:54:57,7, GSM0: -> AT+CREG?
2022-11-14 09:54:57,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:55:05,7, GSM0: <- +CSQ: 18,99 OK OK +CREG: 2,5, 2A3F, 0 OK
2022-11-14 09:55:05,3, GSM0: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying
2022-11-14 09:55:06,7, GSM0: -> AT+CSQ
2022-11-14 09:55:06,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:55:16,7, GSM0: <- +CSQ: 18,99 OK
2022-11-14 09:55:16,5, GSM0: Signal Strength Indicator: (18,99) -77 dBm (Good), Bit Error Rate: not known or not detectable
2022-11-14 09:55:16,7, GSM0: -> AT+CREG?
2022-11-14 09:55:16,7, GSM0: Command is sent, waiting for the answer
2022-11-14 09:55:19,7, GSM0: <- OK +CREG: 2,5, 2A3F, 0 OK
2022-11-14 09:55:19,5, GSM0: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 7. TIME
...
I have taken a look at this forum for similar issues but all the workarounds were not useful. There is an existing topic for the same device, but there are no updates so far. Is there someone successful with this GSM dongle?
Thanks in advance!
|
Page: 1
Time in this board is UTC.
|
|
|
 |
|
|
 |
|
