SMS Server Tools 3
This site is hosted by Kekekasvi.com
 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. Please login or register. Sat Oct 19, 2019 02:48
SMSTools3 Community » Feature requests Bottom

Config file includes + new SIM trigger

Login and Post Reply

Page:  1

Author Post
Member
Registered:
Oct 2018
Location: Netherlands
I have 2 features that I for sure could use :)

Small overview of what I use:
Raspberry Pi with a 16-SIM modem connected.
Each time an SMS is received a PHP script is called, SMS details are parsed and processed. So far all is perfect!
But.. Sometimes I would like to add more SIM cards, or replace etc.

What I would like:
- Some sort of eventhandler call that triggers when a SIM is taken out (or not working, etc). And also a call when a SIM is inserted.
That way I can order the modem to send an SMS to another modem, through that process I can automatically collect the MSISDN.
Send an SMS to the new SIM and collect the IMSI too.

- When I have all that data, I would like to automatically create the config file with the updated details (As I use the number = xxxx, I need to update the config).
So, I now have this:

[default]
init = ...
baudrate = 115200
incoming = high

[GSM1]
device = ...
number = xx
[GSM2]
device = ...
number = xx

etc.
 
'smsdconf' Syntax Highlight powered by GeSHi


I would like this:
[default]
init = ...
baudrate = 115200
incoming = high

[GSM1]
include = /var/conf/GSM1.conf
[GSM2]
include = /var/conf/GSM2.conf
etc.
 
'smsdconf' Syntax Highlight powered by GeSHi


That way I can create the conf for each modem through automated processes. Restart sms3 and be on my way....
I can include 16 confs, 1 for each modem and only update the modem conf when needed.

Hope this makes sense?

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Please test if check_sim feature works with your modems. If it works, an alarmhandler can be used to detect when the SIM is taken out. There is an alarm "Check SIM returned ERROR, try: n" available, but no alarm when the SIM is working again. We can add this alarm later, if this feature is going to be used.

Perhaps more controlled way is to use the suspend file. It ensures that the SIM is not sending/receiving when it's taken out. Also the settings read_configuration_after_suspend and read_identity_after_suspend are available. Please check if suspending is useful for you.

I have to think config file includes later, as it's not a small change. At the moment you could consider to modify the sms3 script. Add something like cat /var/conf/global.conf /var/conf/default.conf /var/conf/GSM*.conf > /etc/smsd.conf just before $DAEMON $ARGS is called.

Member
Registered:
Oct 2018
Location: Netherlands
Topic owner
That idea of combining configs in 1 is actually quite briliant... :shock:
That will solve that issue for me completely.
Thanks (again..!) for the insight.

I will start testing with the alarmhandler and the other config options you have mentioned.
Have some other ideas now aswel to fetch the details of the inserted sims on startup.

So none of the new features I described are needed for now :)

Login and Post Reply

Page:  1

SMSTools3 Community » Feature requests Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.