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. Sun Jun 01, 2025 14:54
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
biboubier: Raspbian GNU/Linux 9 (stretch): 3.1.21: Smsd installed from sources Huawei e3531 Interface : USB Good morning everyone ! Once I reboot my raspberry; this is what I can find in the smsd logs : 2019-10-20 12:42:33,7, MODEM1: Command is sent, waiting for the answer. (15) 2019-10-20 12:42:48,7, MODEM1: No answer, put_command expected (OK)|(ERROR)|(0)|(4), timeout occurred. 3 And this never stops. In order to have the modem responding to commands, I have to manually unplug it and plug it again. Once I unplugged and plugged again the modem, and restart smsd; it works fine. This situation is a bit annoying for me, since I would like the setup to be able to recover on its own. I use one raspberry, which is connected to a sitecom USB hub. The sitecom USB Hub is connected to the power also; in order for the modem to receive the proper energy it needs. The Huawei modem is connected to the sitecom USB Hub. Raspbery > USB Hub > Huawei e3531 I have a file which turns the device into "huawei" under /dev, and smstools is connecting to this one. /etc/udev/rules.d/99-usb-serial.rules SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", SYMLINK+="huawei" I am suspecting that scripts and services are not launching in the correct order, which could maybe explains that the modem does not answer. But that's just a theory; I am not sure what is wrong. I am not sure where to start in order to troubleshoot this problem. I was wondering if maybe you had a hint :) ? Here is my smsd config : #Main config devices = MODEM1 loglevel = 7 # logfiles stats = /var/log/sms/stats logfile = /var/log/sms/smsd.log #All alarms will trigger script alarm_handler.sh alarmhandler=/root/raspnode/alarm_handler.py #All new sms status will trigger event_handler.py script eventhandler=/root/raspnode/event_handler.py incoming_utf8 = yes # Default queue directory = /var/spool/sms outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent # report folder report = /var/spool/sms/report delaytime = 2 errorsleeptime = 10 blocktime = 180 autosplit = 3 #receive_before_send = yes incoming_utf8 = yes [queues] MODEM1=/var/spool/sms/gsm1-1 # Modems configurations [MODEM1] queues=MODEM1 device = /dev/huawei read_timeout = 15 #HUAWEI E3531 init = AT+CNMI=2,0,0,2,1 incoming = yes check_sim=yes report = yes pin = xxxx decode_unicode_text = yes cs_convert = yes pinsleeptime = 2 #350 sms per days max message_limit = 320 message_count_clear = 1450 #report = yes #For development purpose : modem_disabled = no #report_device_details = yes #routed_status_report_cnma = yes primary_memory = SM Thank you in advance for your help !! Cheers Biboubier

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.