SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Wed Mar 12, 2025 20:09
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
fow0ryl: I have included the CFUN and CREG commands into my config file now. This solution of course forces many complete resets ... But after doing this, the system ist running stable for weeks now. Maybe this solutions helps someone else. # # Description: smsd configuration file for HUAWEI E160/E173 USB-Stick devices = SURFSTICK incoming = /run/sms/incoming outgoing = /run/sms/outgoing checked = /run/sms/checked failed = /run/sms/failed sent = /run/sms/sent eventhandler = /etc/scripts/smsd_event.sh alarmhandler = /etc/scripts/smsd_alarm.sh receive_before_send = no autosplit = 3 logfile = 1 loglevel = 5 delaytime = 20 hangup_incoming_call=yes [SURFSTICK] init = AT+CFUN=0;+CFUN=1;+CREG=0;+CREG=1;+CREG=2;+CPMS="ME","ME","ME";+CSCS="GSM";+CNMI=2,0,0,2,1 init2 = AT^CURC=0;^BOOT=0,0 device = /dev/ttyUSB0 incoming = yes check_network = 1 memory_start = 0 check_memory_method = 2 detect_unexpected_input = yes device_open_alarm_after = 3 device_open_retries = 6 report_device_details = yes
fow0ryl: @keke Thank you for this information. Maybe it would be helpful to add this infos to "How to configure". Just to prevent stupid questions, like mine ...
fow0ryl: I can not find a explanation about init and init2 In how to configure there is nearly nothing about that. "most users do not need this" at init2 is not really helpful .... What is the difference between init and init2? Why should I use init2? Is there a limit of characters in each init string? Will init2 command only run, if init is OK? Most items for HUAWEI modems refer to init2 = AT^CURC=0 Regardless of the effect of that command. Why not simply concat this to "init"? Hope that someone can clarify this.
fow0ryl: Ok, frustrating. Receiving stops sometimes even if registration did not change .... I have created a test-reset-script, to reset the E173 stick. reset_e173.sh #!/bin/sh # Modem device DEV=/dev/ttyUSB0 # we need to put sleep n to slow down commands for modem to process echo -e "ATZ\r" >$DEV sleep 1 echo -e "AT+CFUN=0\r" >$DEV sleep 1 echo -e "AT+CFUN=1\r" >$DEV sleep 3 echo -e "AT+CREG=0\r" >$DEV sleep 1 echo -e "AT+CREG=1\r" >$DEV sleep 2 echo -e "AT+CREG=2\r" >$DEV exit 0 I have to stop smstools3, run the script, and start smstools3 again. This way receiving works again, until sometimes. /etc/init.d/smstools3 stop /etc/myscripts/reset_e173.sh /etc/init.d/smstools3 start I found that it does not work, when I did a AT+CREG=2 without a AT+CREG=1 before !!! I wonder if its possible to "reset" precautionary and regulary within smstools?
fow0ryl: I have used a Archer C7 V5 now. SMS receiving did not work after about 8 hours :( Of course I have checked the procedure using an activ hub. No difference. Today I have stopped smstools3 service and played around with some AT commands using picocom. AT+CFUN=0, AT+CFUN=1, AT+CREG=0, AT+CREG=1, AT+CREG=2, .... After playing around and starting smstools3 again after beeing frustrated I found, that all missing SMS are received. And wow. This was the first time I did not have to remove and replug the stick! So I took a look at some saved logs again. I Found that the response to AT+CREG was different sometimes. Of course I did not move the stick in any way. And if it was "CREG: 2,1, 5730, 9AF OK" receiving SMS seems to work. Wed Oct 12 19:37:03 2022 daemon.info smsd[25149]: 2022-10-12 19:37:03,6, SURFSTICK: Checking if Modem is registered to the network Wed Oct 12 19:37:03 2022 daemon.info smsd[25149]: 2022-10-12 19:37:03,7, SURFSTICK: -> AT+CREG? Wed Oct 12 19:37:03 2022 daemon.info smsd[25149]: 2022-10-12 19:37:03,7, SURFSTICK: Command is sent, waiting for the answer. (10) Wed Oct 12 19:37:03 2022 daemon.info smsd[25149]: 2022-10-12 19:37:03,7, SURFSTICK: <- +CREG: 2,1, 5730, 9AF OK Is it possible, that the stick sometimes connects to an unusable network, even if it says "registered"?
fow0ryl: Tried an E173 Stick. But after a week without problems ist stops working too. Next step is to use a Archer C7 instead of the R2S ...
fow0ryl: Hi, I'm trying to get a Huawei E160 work on my NanoPi R2S OpenWrt Router. OpenWrt Version is 21.01.3 smsd Version 3.1.21 (okpg package) Here is my config: devices = E160 incoming = /run/sms/incoming outgoing = /run/sms/outgoing checked = /run/sms/checked failed = /run/sms/failed sent = /run/sms/sent eventhandler = /etc/scripts/smsd_event.sh alarmhandler = /etc/scripts/smsd_alarm.sh receive_before_send = no autosplit = 3 logfile = 1 loglevel = 6 [E160] init = AT^CURC=0 init = AT+CPMS="ME","ME","ME" init2 = AT^BOOT=0,0 device = /dev/ttyUSB0 incoming = yes check_network = 1 check_memory_method = 2 detect_unexpected_input = no device_open_alarm_after = 3 device_open_retries = 6 report_device_details = yes The modem receives SMS as expected after plugging in. But after a couple of hours it stops receiving. When looking into the log everything seems ok Tue Sep 27 13:04:54 2022 daemon.info smsd[31553]: 2022-09-27 13:04:54,6, E160: Checking device for incoming SMS Tue Sep 27 13:04:54 2022 daemon.info smsd[31553]: 2022-09-27 13:04:54,6, E160: Checking if modem is ready Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Pre-initializing modem Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Initializing modem Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Signal Strength Indicator: (18,99) -77 dBm (Good), Bit Error Rate: not known or not detectable Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Checking if Modem is registered to the network Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Modem is registered to the network Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Selecting PDU mode Tue Sep 27 13:04:55 2022 daemon.info smsd[31553]: 2022-09-27 13:04:55,6, E160: Checking memory size Tue Sep 27 13:04:56 2022 daemon.info smsd[31553]: 2022-09-27 13:04:56,6, E160: No SMS received When I unplug and replug the modem, all missing SMS are read. How to find the problem?

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.