Operating system name and version: Debian Stable/Lenny
Version of smsd: 3.1-2+lenny
Smsd installed from: package repository
Name and model of a modem / phone: Motorola K1
Interface: Bluetooth

"Resource temporarily unavailable." Which Resource is this?
Looks like it is always the 6th char where the connection drops.
I always have 2 smstools daemons running after smstools start.
I tried smstools 3.1.6: same. Played with baudrate, rtscts, send_delay, no change. All other phones work nicely.

Thanks for any help.

smsd.conf:
[GSM1] init = ATE0 device = /dev/rfcomm0 incoming = yes #pin = baudrate = 115200

smsd.log:
2010-03-01 09:34:37,2, smsd: Smsd v3.1 started. 2010-03-01 09:34:37,2, smsd: Running as smsd:dialout. 2010-03-01 09:34:37,6, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2010-03-01 09:34:37,6, GSM1: Modem handler 0 has started. PID: 4276. 2010-03-01 09:34:37,6, smsd: Outgoing file checker has started. PID: 4275. 2010-03-01 09:34:38,6, GSM1: Checking device for incoming SMS 2010-03-01 09:34:38,6, GSM1: Checking if modem is ready 2010-03-01 09:34:38,7, GSM1: -> AT 2010-03-01 09:34:38,7, GSM1: Command is sent, waiting for the answer 2010-03-01 09:34:38,7, GSM1: <- AT OK 2010-03-01 09:34:38,6, GSM1: Pre-initializing modem 2010-03-01 09:34:38,7, GSM1: -> ATE0+CMEE=1 2010-03-01 09:34:38,3, GSM1: Could not send character C, cause: Resource temporarily unavailable 2010-03-01 09:34:48,6, GSM1: Initializing modem 2010-03-01 09:34:48,7, GSM1: -> ATE0 2010-03-01 09:34:48,7, GSM1: Command is sent, waiting for the answer 2010-03-01 09:34:49,7, GSM1: <- ATE0 ERROR 2010-03-01 09:34:59,7, GSM1: -> ATE0 2010-03-01 09:34:59,7, GSM1: Command is sent, waiting for the answer 2010-03-01 09:34:59,7, GSM1: <- OK 2010-03-01 09:34:59,6, GSM1: Checking if Modem is registered to the network 2010-03-01 09:34:59,7, GSM1: -> AT+CREG? 2010-03-01 09:34:59,3, GSM1: Could not send character E, cause: Resource temporarily unavailable 2010-03-01 09:35:09,3, GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying 2010-03-01 09:35:10,7, GSM1: -> AT+CSQ 2010-03-01 09:35:10,3, GSM1: Could not send character Q, cause: Resource temporarily unavailable 2010-03-01 09:35:20,7, GSM1: -> AT+CREG? 2010-03-01 09:35:20,3, GSM1: Could not send character E, cause: Resource temporarily unavailable 2010-03-01 09:35:30,3, GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying 2010-03-01 09:35:31,7, GSM1: -> AT+CSQ 2010-03-01 09:35:31,3, GSM1: Could not send character Q, cause: Resource temporarily unavailable 2010-03-01 09:35:41,7, GSM1: -> AT+CREG? 2010-03-01 09:35:42,3, GSM1: Could not send character E, cause: Resource temporarily unavailable 2010-03-01 09:35:52,3, GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying 2010-03-01 09:35:53,7, GSM1: -> AT+CSQ 2010-03-01 09:35:53,3, GSM1: Could not send character Q, cause: Resource temporarily unavailable ...

If you have already tried with send_delay = 0 setting and got "Could not send string...", smsd cannot fix this error. A message "Resource temporarily unavailable" comes from the operating system and you have a permanent problem with bluetooth.

While all other phones work, do you use bluetooth with them or some other interface?

Your note about send_delay = 0 gave me the hint it had to do with this.

This smsd.conf did it for my Motorola K1. I had to add the secontary_memory_max thing else I got +CMS ERROR 305 and 321.
Now all 3 phones work perfectly on one usb bt. /dev/rfcom0 - 2

Thanks a lot great tool!

[GSM1]
init = ATE0
device = /dev/rfcomm0
secondary_memory_max = SM,SM,SM
incoming = yes
baudrate = 115200
send_delay = 50

The setting secondary_memory_max in an integer value, and in your case it gets a value 0. However, it is not even used because you do not have dual-memory handler in use.

And as you have not disabled the pre_init, you do not need to use init = ATE0 because pre-initialization does it.

Anyway, good to know that your system works well now, even with bluetooth (which is often problematic).