SMS Server Tools 3
This site is hosted by
Basic information:
Additional information:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

Custom Search

 Visitor locations
 SMS Server Tools 3 Community
Welcome, Guest. Please login or register. Sun May 19, 2024 21:27
SMSTools3 Community » Bug reports Bottom

Modem handler terminated due to not reaching modem

Login and Post Reply

Page:  1

Author Post
Oct 2023
Location: Germany
I am using the latest SMS Server Tools 3 with Debian 12 from Debians official packet repo.
I installed to use it with a LTE LAN Gateway, using Telnet/TCP to communicate.
Basic communication works with following configuration:

# /etc/smsd.conf
# Description: Main configuration file for the smsd

devices = GSM1
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
incoming = /var/spool/sms/incoming
logfile = /var/log/smstools/smsd.log
infofile = /var/run/smstools/smsd.working
pidfile = /var/run/smstools/
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
stats = /var/log/smstools/smsd_stats
loglevel = 7
receive_before_send = no
autosplit = 3

device = @IP:PORT
device_open_errorsleeptime = 5
device_open_retries = -1
incoming = no
keep_open = no
report_device_details = yes
regular_run_interval = 60
regular_run_cmd = AT+CREG?;+CSQ;+COPS?
regular_run_statfile = /dev/shm/sms_stat
'smsdconf' Syntax Highlight powered by GeSHi

Problem is that I'd like in every scenario (network down/maintenance, LTE modems reset, something gets unplugged for a second) - SMS Server Tools 3 should be retrying to connect and sent the SMS for all eternity.

However, if I do following:
- Start SMS Server Tools 3
- we can also test send an SMS, everything will be fine here
- Then connect to the LTE modem via telnet myself and with that blocking connection from the smsd
- Putting a new SMS in
- If at this point, within some seconds I do not end the telnet session and "free it up", it will end up in this cycle:

Note that, the service was configured to never give up, and retry again and again - however, after one minute it does disables the modem handler permanently and never recovers. Only if I restart the complete service it will send out the SMS. How can we fix that?

Thanks a lot

May 2009
Location: Jyväskylä, Finland
In this case, the naming of the smsd settings may not be as clear as possible. When the device is a socket, the settings that affect it are called socket_connection_alarm_after, socket_connection_errorsleeptime and socket_connection_retries. I don't remember why these were given their own names back in the day. But using these you may make the daemon try endlessly.

However, some possible errors are such that smsd cannot handle them. It would be a good idea to use the alarmhandler feature and monitor what kind of notifications smsd gives in different situations. A situation where smsd does not resolve itself can be solved in a suitable way and, for example, get smsd to restart if necessary.

Parameters of alarmhandler are documented here.

Oct 2023
Location: Germany
Topic owner
Excellent, thank you very much, with changes to the socket_connection parameters it works.
Sorry for my oversight! :)

Login and Post Reply

Page:  1

SMSTools3 Community » Bug reports Top

Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.