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. Tue Jul 01, 2025 02:07
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
Sallinen: You have two ways: 1. aliases: /etc/aliases: smsd: | /usr/share/smstools/scripts/email2sms What that will do it will pipe all incoming mail for smsd user to email2sms script. 2. Use procmail delivery the email to the user, add this to smsd users .procmailrc: # cat .procmailrc VERBOSE=off MAILDIR=$HOME/Maildir/ DEFAULT=$HOME/Maildir/ LOGFILE=$HOME/procmail/log :0 * | /usr/share/smstools/scripts/email2sms That will essentially do the same, but with logging if something goes b0rk. I have set up the same thing, the script will pick the destination from To: field, ie. To: 358407007600@foobar.com and use that as Destination number. ps. email2sms script file has few examples, including procmail one that I mentioned.
Sallinen: yeah, here we go: devices = GSM1 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed sent = /var/spool/sms/sent incoming = /var/spool/sms/incoming logfile = /var/log/smsd.log loglevel = 5 checkhandler = /opt/gnu/share/smstools/scripts/checkhandler-multirecip [GSM1] device = /dev/cua/b incoming = yes check_memory_method = 31 # init = AT+CPMS="SM" init = AT+CPMS="MT","MT","MT" pin = 1234 hangup_incoming_call = yes report = yes ps. commented #check_memory_method, aka. moved to default one and all the status reports we're received properly!
Sallinen: Continued from my last topic, which has been now marked as inactive (We don't send mass sms's that often;) Here's an private link to Keke to our sms.log with log-level 7. ( PRIVATE BLOCK ) It seems that after sending out +30 2-part SMS's we are unable to receive SMS, ie. no status reports received or anything :O
Sallinen: Ah I had almost forgotten the issue :-D We will be having scheduled maintenance tomorrow and I will be informing our users by SMS, so I will try the new init-string and loglevel 7 when sending the mass SMS tomorrow - I'll post the log. And no, we won't be quittig on MC35i and SMSTools, best combo ever!
Sallinen: AT+CNMI=? +CNMI: (0-3),(0,1),(0,2,3),(0,2),(1) OK AT+CNMI? +CNMI: 0,0,0,0,1
Sallinen: I'll do loglevel 7 when I'm sending "mass-sms" next time.
Sallinen: ( PRIVATE BLOCK ) Yes, I used check_memory_method = 31 and report = yes options.
Sallinen: Operating system name and version: Solaris 10 Version of smsd: 3.1.5 Smsd installed from: sources Name and model of a modem / phone: Siemens MC35i Interface: serial I was sending 40 SMS's to different phone numbers, I got 3-4 of these messages into log: CMGL handling error: Line end not found (PDU) Unexpected input: +CMGL: 16,0,,167 +CMGL: 17,0,,167 +CMGL: 22,0,,167 What does that actually mean? Didn't I terminate the textfile correctly while editing it in vi?
Sallinen: Oh well, why not just use check_memory_method = 31 :-)
Sallinen: So when smstools reads/receives the message from the modem the message is deleted, right? In that case there isn't any problem since I run smstools 24/7.
Sallinen: You could try with init = AT+CPMS="MT","MT","MT", if not already tried. Ah, thanks! That did the job :-) Does AT+CPMS="MT","MT","MT" clear the SIM and Modem memory when Sending and Receiving SMS's? ie. would I have trouble when memory fills, if I use check_memory_method 1: CPMS?
Sallinen: Operating system name and version: Solaris 10 Version of smsd: 3.1.5 Smsd installed from: sources Name and model of a modem / phone: Siemens MC35i Interface: serial I can't receive SMS's with my Siemens MC35i running smsd 3.1.5. Here's my smsd.conf: devices = GSM1 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed sent = /var/spool/sms/sent incoming = /var/spool/sms/incoming logfile = /var/log/smsd.log loglevel = 5 admin_to = +35840xxxxxxx checkhandler = /opt/gnu/share/smstools/scripts/checkhandler-multirecip [GSM1] device = /dev/cua/b incoming = yes init = AT+CPMS="SM" pin = xxxx hangup_incoming_call = yes smsd gives following when using "SM": 2010-03-21 09:52:39,7, GSM1: <- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30 OK when using "SM","SM","MT" it gives following: 2010-03-21 09:48:24,7, GSM1: <- +CPMS: "SM",0,30,"SM",0,30,"MT",11,55 OK So there's messages in the modems memory. I tried check_memory_method = 3 (and 31, 5 etc) but it didn't do any good. Default check_memory_method is 1. Yours, Jussi Sallinen.

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.