Operating system name and version: Linux Mint 17.2 on Fitlet -B Barebone
Version of smsd: v3.1.15
Smsd installed from: package repository
Name and model of a modem / phone: Wavecom Fastrack
Interface: USB

Hi all

First time user of this modem, although used AT commands 30+ years ago.
Newbie to Linux as well, but slowly getting there.
2015-10-18 13:26:42,2, smsd: Smsd v3.1.15 started. 2015-10-18 13:26:42,2, smsd: Running as smsd:dialout. 2015-10-18 13:26:42,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.xbXrHc /tmp/smsd_data.c5mptH 2015-10-18 13:26:42,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2015-10-18 13:26:42,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2015-10-18 13:26:42,5, smsd: Outgoing file checker has started. PID: 1605. 2015-10-18 13:26:42,7, smsd: All PID's: 1605,1606 2015-10-18 13:26:42,5, GSM1: Modem handler 0 has started. PID: 1606. Will only send messages. 2015-10-18 13:26:42,6, GSM1: Checking if modem is ready 2015-10-18 13:26:43,7, GSM1: -> AT 2015-10-18 13:26:43,7, GSM1: Command is sent, waiting for the answer 2015-10-18 13:26:43,7, GSM1: <- AT OK 2015-10-18 13:26:43,6, GSM1: Pre-initializing modem 2015-10-18 13:26:43,7, GSM1: -> ATE0+CMEE=1;+CREG=2 2015-10-18 13:26:43,7, GSM1: Command is sent, waiting for the answer 2015-10-18 13:26:43,7, GSM1: <- ATE0+CMEE=1;+CREG=2 OK 2015-10-18 13:26:43,6, GSM1: Checking if modem needs PIN 2015-10-18 13:26:44,7, GSM1: -> AT+CPIN? 2015-10-18 13:26:44,7, GSM1: Command is sent, waiting for the answer 2015-10-18 13:26:44,7, GSM1: <- +CPIN: READY 2015-10-18 13:26:44,6, GSM1: Initializing modem 2015-10-18 13:26:44,7, GSM1: -> ATZ 2015-10-18 13:26:44,7, GSM1: Command is sent, waiting for the answer 2015-10-18 13:26:44,7, GSM1: <- OK 2015-10-18 13:26:45,7, GSM1: -> AT+CSQ 2015-10-18 13:26:45,7, GSM1: Command is sent, waiting for the answer 2015-10-18 13:26:45,7, GSM1: <- AT+CSQ +CSQ: 22,0 OK 2015-10-18 13:26:45,6, GSM1: Signal Strength Indicator: (22,0) -69 dBm (Excellent), Bit Error Rate: less than 0.2 % 2015-10-18 13:26:45,6, GSM1: Checking if Modem is registered to the network 2015-10-18 13:26:45,7, GSM1: -> AT+CREG? 2015-10-18 13:26:45,7, GSM1: Command is sent, waiting for the answer 2015-10-18 13:26:45,7, GSM1: <- AT+CREG? +CREG: 0,1 OK 2015-10-18 13:26:45,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 1. TIME

If I use the package that came with the modem (smscaster) then I can send sms's without a problem.
The config file below.(only enabled lines shown)
I added some line after browsing the problem.
# # /etc/smsd.conf # # Description: Main configuration file for the smsd # devices = GSM1 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked incoming = /var/spool/sms/incoming logfile = /var/log/smstools/smsd.log infofile = /var/run/smstools/smsd.working pidfile = /var/run/smstools/smsd.pid 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 stats = /var/log/smstools/smsd_stats loglevel = 7 smart_logging = yes [GSM1] init = ATZ device = /dev/ttyUSB0 incoming = no #pin = baudrate = 115200

The log line of MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 1. TIME
repeats 25 times before quiting.

Is there something obvious here to you guys or is more information needed ?
Does someone have a config file for this modem ?

Hi All

Couldn't find an Edit buton for my previous post.
The following is additional info when the unit fails.
2015-10-18 14:08:48,5, GSM1: MODEM IS NOT REGISTERED, WAITING 1 SEC. BEFORE RETRYING 100. TIME 2015-10-18 14:08:49,3, GSM1: Error: Modem is not registered to the network 2015-10-18 14:08:49,2, GSM1: Failed to initialize modem GSM1. Stopping. 2015-10-18 14:08:49,2, GSM1: Modem handler 0 terminated. PID: 1617, was started 15-10-18 14:05:27.

So, obviously it tries 100 times (not 25) , and this time I left a file to send.
When it quit, it moved the file to /checked/ which surprised me as I would have expected it to end up
in /Failed/

Hi,

First the modem is pre-initialized, but as you have init = ATZ setting, reset is done later. This causes that echo returns on. Usually it should not cause troubles, but it's still better that echo is off. Remove init setting and try once again.

The modem is registered, but smsd does not see that. Assuming that the problem continues even when init setting was removed, use a global setting log_read_from_modem = yes and try once again. It is important to see the log, as there is a hex dump which will show it there are some unexpected characters in the response.

If the problem still continues, you can disable checking with a modem setting check_network = no. This is a temporary work-around, but you could use it while waiting for the complete solution.

Mainprocess picks up messages and moves them to the spooler (checked). Mainprocess does not care about them later. Modem processes are trying to send them, and it the sending fails, they are moved to failed folder. In this case sending was not even started, as the initialization failed. Message is not moved, because there may be some more modem processes which are serving the same queue and message will be handled by one of them.

Hi All

keke, many thanks for that.
I did two things.
1: I added the smsc after finding it with "smscaster" on Xp
However, it reported a number like +131********
I put the + in front of the number, does that make any difference ?

2. As per your suggestion removed the init.

And it worked after I re-booted.

Just for members information, I will be using this to send report strings from machines in production.
Being able to just copy a file to a folder, and everything is done, is just brilliant.
Otherwise I would have to do all the AT commands from within my software.

Now that I am a member of this forum, I will keep an eye out.

Thank you once again.

+ sign in the smsc definition is not required, but can be used because it is removed when the number is processed.

Thank's for choosing this software.