| Keywords: Mode: All keywords (AND) |
|
Wed Apr 27, 2016 08:45
|
hakash: Operating system name and version: Linux ( old gentoo, will be migrating soon )
Version of smsd: 3.1.11
Smsd installed from: sources
Name and model of a modem / phone: Cinterion MC55i (siemens compatible)
Interface: tcp to serial
I have been running SMS Server Tools for years now serving up messages for logging on to the wireless guest network of the company I work at. It's been working great so far, but I'm starting to have issues with load. We are now peaking login requests in periods at 1 request every 1-5 seconds and it's making my server sad. The one modem I have had handling this load up until now has managed quite nicely, but after a change in the wireless setup which pushed about twice as man users over to the guest portal rather than 802.1X, the modem cant send the messages fast enough.
Fair enough, simple solution, add mode modems. Or so I thought... My setup is now, 1 common queue and two modems both configured to handle the queue, no providers, only one modem configured to receive mesages. The SIMs are twin-SIMs sharing the same phone number. All messages are moved from the outgoing folder to the queue folder correctly.
The problem is that one modem is diligently handling the queue, but the other modem is only occasionally handling outgoing messages. The lazy modem is the one handling incoming messages, but the logs show that there are almost never any incoming messages, but it does check.
How can I make the lazy modem handle messages when there are messages not being handles by the other modem? If there are 2 messages, one locked by the other modem, I am expecting the lazy modem to handle it, but in reality it checks to see if there are any messages and does nothing. My queue is in other words building up to a queue in the hundreds, especially when users start hammering the login buttons to get the codes that never arrive due to the long queue...
Thank you again for a great product, and to anyone willing or able to assist me here.
Config:
devices = GSM2,GSM3
outgoing = /var/spool/sms/outgoing
checked = /var/spool/sms/checked
failed = /var/spool/sms/outgoing
incoming = /var/spool/sms/incoming
loglevel = 7
alarmlevel = 4
delaytime = 6
delaytime_mainprocess = 1
errorsleeptime = 10
blocktime = 120
eventhandler = /var/www/localhost/htdocs/smsevent
receive_before_send = no
autosplit = 3
ignore_outgoing_priority = yes
spool_directory_order = no
[queues]
Main = /var/spool/sms/outgoing/Main
[GSM2]
queues = Main
init = AT+CPMS="SM","SM","SM"
device = @x.x.x.x:950
incoming = no
pin = XXXX
baudrate = 115200
rtscts = yes
cs_convert = yes
report = no
hangup_incoming_call = yes
keep_open = no
[GSM3]
queues = Main
init = AT+CPMS="SM","SM","SM"
device = @x.x.x.x:950
incoming = high
pin = XXXX
baudrate = 115200
rtscts = yes
cs_convert = yes
report = no
hangup_incoming_call = yes
keep_open = yes
|
|
Tue Oct 12, 2010 15:40
|
hakash: Thank you so much for that fast reply!
I have obviously misunderstood exactly how the server goes throught its checklist of what to do. I understood it so that the delaytime was for checking the outgoing folder for new items. :oops:
Now I understand the flow of the application a bit better. Thank you again!
Cheers!
|
|
Tue Oct 12, 2010 13:13
|
hakash: Operating system name and version: Gentoo (unknown version)
Version of smsd: 3.1.11
Smsd installed from: sources
Name and model of a modem / phone: 2x Cinterion MC35i + 1x ETM9300-1
Interface: sockets via Moxa 6150
Hi,
I have had your server running for a few months now as a SMS-Server for sending passwords for user logging in to a wireless hotspot using the two Cinterion modems. We are planning to add a few new features for some of our customers (password reset via SMS for example). For this we are thinking of setting up the ETM modem as a dedicated reciever.
In this regard I have a couple of questions.
1. I have read the config-files up and down several times, but I can't seem to find a setting for how often the modem is checked for new messages. How to I set this in the config? Is it possible to check new messages without sending? Only documentation I can find states that new messages are check either before or after sending, and that it checks for new messages to send in the spooler directory. If there are noe files, it sleeps again. Is this correct?
2. Will I be able to use the keep_open = no setting with this configuration? Reason is when the Moxa-box is reset the servers deviceprocesses crashes since it cuts the open tunnelt throught the box. It works well for sending, but I'm worried about not being able to detect incomming SMS without an open connection.
3. What kind of load does an interval of 1-3 seconds between checking for new SMS have on the server? As mentioned above, I have only 3 devices to run, two are dedicates senders, and one will be dedicated receiver. The server it self does nothing else except running as a LAMP-server as well, where we only use an URL2SMS variant via https. MySQL does nothing in this scenario, and probably won't for a while either.
Hope you can help!
PS! I want to thank you for your excellent work with this server, it is a really powerful tool, and when the MySQL integration comes for spooling, it will be almost unrivaled :mrgreen:
|
