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. Fri Aug 29, 2025 21:14
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
kuula: Haa! Thanks. It seems to be working correctly with alarmlevel = DEBUG. Maybe I had the alarmlevel set to something else than the default as a test but forgot to actually make the change later on. Does the DEBUG level take care of all the other alarms too? If some day in the future it throws something else than the "write_to_modem" error. On a side note, this required me to reboot as the debian-provided /etc/init.d/smstools script seems to be buggy and didn't want to restart smsd. But anyway, I'm a happy smstools user now ;)
kuula: There's no mention of running alarmhandler in the log. Just "write_to_modem: device busy, waiting" and then "Moved file /var/spool/sms/outgoing/something to /var/spool/sms/checked". Sorry I can't get the actual log here now. That output comes after the modem state has been checked "Checking if modem is ready -> AT". The modem is busy, yes, the machine uses it as the primary link to the internet. But that's where the alarmhandler and my other script should come in. I haven't put up any eventhandlers of my own.
kuula: Operating system name and version: Debian lenny kernel: 2.6.26-2-686 Version of smsd: 3.1.11 Smsd installed from: Debian lenny-backports repository Name and model of a modem / phone: Sierra Wireless Compass 889 Interface: USB Smstools doesn't properly call alarm handler in my case. I use the alarm handler to create a file that is checked by another script (this then kicks smstools among other things to try and resend a failed message). The scripts shouldn't be the problem though as they're not called at all. And they did work on another machine running the same setup but 2.6.26-2-486 kernel. I actually had the same problem on another installation (with the 486 kernel) too, but it resolved itself when I re-installed the OS (to test some other stuff). So I figured I had something weird in my installation, but now this haunts me again. Any ideas? Would love to use the alarm handler as it worked so flawlessly before.

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.