Operating system name and version: Centos 6
Version of smsd:3.1.5
Smsd installed from: sources / package repository / from elsewhere...
Name and model of a modem / phone: Samsung flip phone
Interface: USB

All,

I'm trying to figure out if I can use our "old" samsung flip cellphone for SMSTOOLS.

Seem like smstool is having a hard time to communicate with the modem itself.

Here's the log:

2016-11-22 16:14:41,2, smsd: Running as root:root. 2016-11-22 16:14:41,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.OCTplJ /tmp/smsd_data.dyLiip 2016-11-22 16:14:41,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2016-11-22 16:14:41,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2016-11-22 16:14:41,5, smsd: Outgoing file checker has started. PID: 31728. 2016-11-22 16:14:41,5, GSM101: Modem handler 0 has started. PID: 31729. 2016-11-22 16:14:41,7, smsd: All PID's: 31728,31729 2016-11-22 16:14:41,5, GSM101: Using check_memory_method 2: CMGD is used. 2016-11-22 16:14:41,5, GSM101: Using read_timeout 20 seconds. 2016-11-22 16:14:41,6, GSM101: Checking device for incoming SMS 2016-11-22 16:14:41,6, GSM101: Checking if modem is ready 2016-11-22 16:14:41,3, GSM101: Unexpected input: OK 2016-11-22 16:14:41,7, GSM101: -> AT 2016-11-22 16:14:41,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:14:42,7, GSM101: <- OK 2016-11-22 16:14:42,6, GSM101: Pre-initializing modem 2016-11-22 16:14:42,7, GSM101: -> ATE0+CMEE=1;+CREG=2 2016-11-22 16:14:42,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:14:42,7, GSM101: <- OK 2016-11-22 16:14:42,6, GSM101: Checking if modem needs PIN 2016-11-22 16:14:42,7, GSM101: -> AT+CPIN? 2016-11-22 16:14:42,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:14:43,7, GSM101: <- +CPIN: READY OK 2016-11-22 16:14:43,7, GSM101: -> AT+CSQ 2016-11-22 16:14:43,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:14:43,7, GSM101: <- +CSQ: 14,99 OK 2016-11-22 16:14:43,6, GSM101: Signal Strength Indicator: (14,99) -85 dBm (Workable), Bit Error Rate: not known or not detectable 2016-11-22 16:14:43,6, GSM101: Selecting PDU mode 2016-11-22 16:14:43,7, GSM101: -> AT+CMGF=0 2016-11-22 16:14:43,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:14:52,5, smsd: Moved file /var/spool/sms/outgoing/send_AxGe0S to /var/spool/sms/checked 2016-11-22 16:15:03,7, GSM101: put_command expected (OK)|(ERROR), timeout occurred. 1. 2016-11-22 16:15:03,7, GSM101: <- 2016-11-22 16:15:04,7, GSM101: -> AT+CMGF=0 2016-11-22 16:15:04,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:15:24,7, GSM101: put_command expected (OK)|(ERROR), timeout occurred. 2. 2016-11-22 16:15:24,7, GSM101: <- 2016-11-22 16:15:24,7, GSM101: -> AT+CIMI 2016-11-22 16:15:24,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:15:44,7, GSM101: put_command expected (OK)|(ERROR), timeout occurred. 3. 2016-11-22 16:15:44,7, GSM101: <- 2016-11-22 16:15:44,7, GSM101: -> AT+CGSN 2016-11-22 16:15:44,7, GSM101: Command is sent, waiting for the answer 2016-11-22 16:16:05,7, GSM101: put_command expected (OK)|(ERROR), timeout occurred. 4. 2016-11-22 16:16:05,7, GSM101: <- 2016-11-22 16:16:05,5, GSM101: CGSN: 2016-11-22 16:16:05,5, GSM101: IMSI: 2016-11-22 16:16:05,6, GSM101: Checking if reading of messages is supported 2016-11-22 16:16:05,7, GSM101: -> AT+CPMS? 2016-11-22 16:16:05,7, GSM101: Command is sent, waiting for the answer

and the config:

# Example smsd.conf. Read the manual for a description devices = GSM101 logfile = /var/log/smsd/smsd.log loglevel = 7 # user = smstools outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent infofile = /var/run/smsd/smsd.working pidfile = /var/run/smsd/smsd.pid # 3.1.5 introduced smart logging # once your configuration is OK, set log level lower (5 is good in most cases) smart_logging = yes [GSM101] device = /dev/ttyACM0 check_memory_method = 2 memory_start = 0 read_timeout = 20 report = yes incoming = yes check_network = 0 baudrate = 9600

If you have any tips, they are welcomed.

Sincerly,
-Francis

Modem stops answering after the command AT+CMGF=0. If this always happens when retrying, I think that nothing can be done.

To make sure, you could try communication with Minicom. If AT gets OK, and AT+CMGF=0 causes freezing the same way, the phone is broken or incompatible. Perhaps PDU mode is not supported.

Followed those instructions since I am not very familiar with the commands
http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/modem-minicom.html

Keep crashing, like you said.

So I guess I will just buy a Wavecom Q24Plus on ebay, since I think this model work pretty well with the tool?

Thank for the prompt reply!
-Francis