I'm running a fairly standard setup on XP with a config as follows:

devices = KGS1
logfile = /var/log/smsd.log
smsloglevel = 5
hangup_incoming_call = yes
report = /var/spool/sms/report
stats = /var/spool/sms/stats
failed = /var/spool/sms/failed
sent = /var/spool/sms/sent
status_signal_quality = no

[KGS1]
device = /dev/com3
init = AT+CPMS="ME"+CMGF=1
incoming = yes
check_network = 0
baudrate = 115200
eventhandler = /usr/local/bin/smsevent
memory_start = 0


I've noticed that smsd will not send until it has cycled through all the mem slots first. Since I've got approx 200 for the memory of my phone, the files sit in the checked directory until this cycle is complete. Is there a better way to prioritize the sending?

I removed +CMGF=1 off the init string and things are running much, much faster now. I'm assuming there's a preference on PDU mode.

finnman wrote

I removed +CMGF=1 off the init string and things are running much, much faster now. I'm assuming there's a preference on PDU mode.

Yes, the smsd uses PDU mode only. This is because the ASCII mode is too limited, and even if ASCII mode is selected, the message is received using PDU mode, if it contains characters outside the GSM alphabet, for example "tab".

Before incoming messages are checked, the PDU mode is selected. Because of this, I'm not sure why your system is much faster now. I was thinking that there is some issue with a message numbers in your phone, but only the piece of a log with loglevel 7 may show exactly what is the issue. It may also be useful to know what is the name and model of your device.

You are running at least the version 3.1.5 of smstools, right? In any case, there is no setting smsloglevel available, and this should cause an error. Perhaps you are running much more older version?

Nope - running the latest and greatest. No problem issues at all since I removed that string. The modem is a ZTE MF627.

I did some other hiccups but I had to kill the 'autorun' feature that was embedded into the modem.