Operating system name and version: Ubuntu 10.10 Desktop x386
Version of smsd: 3.1.10
Smsd installed from: repository
Name and model of a modem / phone: Huawei e1552
Interface: USB

Would anyone have config file for a Huawei E1552? I tried sending an SMS by placing the following in a text (randomfeb5) in /var/spool/sms/outgoing:

Quote

To: 0902XXXXXX (mobile number was placed here)
Flash: no
Alphabet: ISO

Hello Stefan, how are you?

After a couple of seconds, the file was then transferred to /var/spool/sms/checked but no SMS was sent. Nothing was in /var/spool/sms/sent nor did anything arrive in the recipient's mobile phone.

Notice though that I am an absolute newbie (I even copied the sample SMS text message file from http://smstools3.kekekasvi.com/index.php?p=fileformat) so I may be doing something wrong.

I haven't touched the /etc/smsd.conf though so I may doing something wrong.

With Huawei device you have to use a modem setting init = AT^CURC=0, or init2 if init is already used. But this has nothing to do with your current problem.

You could define a global setting failed = /var/spool/sms/failed, and create this directory. Then restart the smsd. Next time when sending fails, message is moved to this directory and there is a header Fail_reason which tells why sending has failed.

Your To: 0902XXXXXX may be a sample, but it does not look correct. Number should be presented using international format, in your country it should start with 63. This may be a reason for the failure, but if the sending with international number still fails, show a piece of log here so I can check what actually is happening.

Thanks for the tips.

I modified my /etc/smsd.conf and the GSM1 setting is now:



I also changed the To part to To: 63902XXXXXX, but still no luck. The /etc/smsd.conf already had a "failed" setting, but even though the message wasn't sent, nothing went into the "failed" folder.

The latest logs show the following:2011-02-05 20:25:21,2, smsd: Smsd v3.1.10 started. 2011-02-05 20:25:21,2, smsd: Running as root:root. 2011-02-05 20:25:21,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2011-02-05 20:25:22,3, smsd: FATAL ERROR: Looks like another smsd (20114) is running. I (18734) quit now. 2011-02-05 20:25:22,2, smsd: Smsd mainprocess terminated abnormally. PID: 18734. 2011-02-05 20:25:26,2, smsd: Smsd v3.1.10 started. 2011-02-05 20:25:26,2, smsd: Running as root:root. 2011-02-05 20:25:26,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2011-02-05 20:25:31,3, smsd: FATAL ERROR: Looks like another smsd (20120) is running. I (20114) quit now. 2011-02-05 20:25:31,2, smsd: Smsd mainprocess terminated abnormally. PID: 20114. 2011-02-05 20:25:57,2, smsd: Smsd v3.1.10 started. 2011-02-05 20:25:57,2, smsd: Running as root:root. 2011-02-05 20:25:57,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2011-02-05 20:25:57,2, smsd: Running in terminal mode. 2011-02-05 20:26:06,3, smsd: FATAL ERROR: Looks like another smsd (20129) is running. I (20120) quit now. 2011-02-05 20:26:06,2, smsd: Smsd mainprocess terminated abnormally. PID: 20120. 2011-02-05 20:26:09,2, smsd: Smsd mainprocess is awaiting the termination of all modem handlers. PID: 20129. 2011-02-05 20:28:02,2, smsd: Smsd v3.1.10 started. 2011-02-05 20:28:02,2, smsd: Running as root:root. 2011-02-05 20:28:02,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2011-02-05 20:28:05,2, smsd: Smsd v3.1.10 started. 2011-02-05 20:28:05,2, smsd: Running as root:root. 2011-02-05 20:28:05,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2011-02-05 20:28:09,2, smsd: Smsd v3.1.10 started. 2011-02-05 20:28:09,2, smsd: Running as root:root. 2011-02-05 20:28:09,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2011-02-05 20:28:12,3, smsd: FATAL ERROR: Looks like another smsd (20284) is running. I (20272) quit now. 2011-02-05 20:28:12,2, smsd: Smsd mainprocess terminated abnormally. PID: 20272. 2011-02-05 20:28:15,3, smsd: FATAL ERROR: Looks like another smsd (20284) is running. I (20278) quit now. 2011-02-05 20:28:15,2, smsd: Smsd mainprocess terminated abnormally. PID: 20278.

I really appreciate all the help. I look forward to sending my first SMS.

Small update: I changed my smsd.conf to



And I was able to get something in the failed folder. Still no sent SMS though.

You had started smsd many times, even when it was already running. If you have some script which does this, please disable it.

The device setting was changed. As it was the first serial port, you likely had communication errors (modem does not answer... ) in the log and therefore no SMS was sent.

Now with the correct device setting communication works. As you have something in the failed folder, what kind is a failed message? What is the Fail_reason? If the reason is not clear, show a piece of log when smsd tries to send a message.

I looked at the smsd logs again (I was surprised that it reached almost 100++MB in less than 30 mins) and saw that it had some errors when writing to the folders. I changed the permissions to 777 (along with changing the baudrate of the E1552 to 9200 or 9600 - I forgot the exact value) and SMS Tools now works perfectly.

I'm going to post another topic though on how to make the folders more secure. Keeping them at 777 doesn't seem like a good idea.