Operating system name and version: Fedora 12 linux
Version of smsd: 3.1.3
Smsd installed from: package repository
Name and model of a modem / phone: Huawei E182E HSDPA dongle
Interface: USB

When running SMS Server Tools 3.1.3 I get the following error log when trying to send an SMS message (reception of messages works fine):

2010-05-30 14:44:51,7, GSM1: <- OK
2010-05-30 14:44:51,6, GSM1: Pre-initializing modem
2010-05-30 14:44:51,7, GSM1: -> ATE0+CMEE=1
2010-05-30 14:44:51,7, GSM1: Command is sent, waiting for the answer
2010-05-30 14:44:51,7, GSM1: <- OK
2010-05-30 14:44:51,6, GSM1: Checking if Modem is registered to the network
2010-05-30 14:44:51,7, GSM1: -> AT+CREG?
2010-05-30 14:44:51,7, GSM1: Command is sent, waiting for the answer
2010-05-30 14:44:52,7, GSM1: <- +CREG: 2,1, 9D6D, 1930F34 OK
2010-05-30 14:44:52,6, GSM1: Modem is registered to the network
2010-05-30 14:44:52,6, GSM1: Selecting PDU mode
2010-05-30 14:44:52,7, GSM1: -> AT+CMGF=0
2010-05-30 14:44:52,7, GSM1: Command is sent, waiting for the answer
2010-05-30 14:44:52,7, GSM1: <- OK
2010-05-30 14:44:52,7, GSM1: -> AT+CMGS=18
2010-05-30 14:44:52,7, GSM1: Command is sent, waiting for the answer
2010-05-30 14:44:52,7, GSM1: <- >
2010-05-30 14:44:52,7, GSM1: -> 0011000A9154040383730000FF05E8329BFD06
2010-05-30 14:44:52,7, GSM1: Command is sent, waiting for the answer
2010-05-30 14:44:52,7, GSM1: <- +CMS ERROR: 330
2010-05-30 14:44:52,7, GSM1: Explanation: SMSC address unknown
2010-05-30 14:44:52,3, GSM1: The modem said ERROR or did not answer.
2010-05-30 14:44:52,5, GSM1: Waiting 10 sec. before retrying

My configuration of smsd looks like this:

[root@localhost incoming]# cat /etc/smsd.conf
# Example smsd.conf. Read the manual for a description

devices=GSM1
incoming=/var/spool/sms/incoming
outgoing=/var/spool/sms/outgoing
checked=/var/spool/sms/checked
sent=/var/spool/sms/sent
logfile=/var/log/smsd.log
delaytime=3
loglevel =7

[GSM1]
device=/dev/ttyUSB3
pre_init=yes
#init=AT+CPMS="SM"
#init2=AT+CSCA="+4531300000"
incoming=yes
outgoing=yes
memory_start=0
baudrate=115200
#baudrate=19200
rtscts=yes
send_delay=1
cs_convert=yes
sending_disabled=no
modem_disabled=no
mode=new
#smsc=4531300000

I have tried to set the SMSC address but get an ERROR on that as well. The strange thing is that it worked fine a few few moths ago???

I would appreciate your kind help in this issue?

Have you checked that the destination number is correct?

Assuming that it's correct, you could check if you can send the SMS using this same SIM in your handset.

Also, using your handset you could check what is the SMSC setting in the SIM and if it's correct for the operator.

Yes, the destination number is correct.

I can send SMS if I insert the SIM card in my SE X1 and also with the Windows PC client.

The AT+CSCA? command in Windows gives the following answer:

17:00:17_500 | 64 | 02 | SmsThread | 0x00000840 |
ace::SerialString::Read | Read: AT+CSCA?

+CSCA: "+4531300000",145

So the problem is somehow Fedora 12 linux related.

Ok. When you tried to set the SMSC, but got an error, you mean that the error was received when trying to send a message, not after CSCA command?

The PDU string is correct, but perhaps it's broken when a modem receives it. Have you tried with a lower baudrate?

The error I got was on the CSCA command, and not when I tried to send a message.

I have tried to set the baudrate to 19200 but no good results.

I also tried to without PIN on the SIM card but then SMS Server tools got on error when asking for the PIN and aborted.

I also changed the PDU encoding from Automatic to GSM (ETSI) but no change.

Strange...

Make this change to the smsd.conf:
init = ATE1+CMEE=1
pre_init = no

I would like to see what the modem echoes back when the smsc is set and/or when a PDU is sent.

cookman wrote

I also tried to without PIN on the SIM card but then SMS Server tools got on error when asking for the PIN and aborted.

Can you show the log containing this error?

Changed the smsd.conf as you told me.
The problem still retains.

2010-05-30 19:42:16,6, GSM1: Checking if modem is ready
2010-05-30 19:42:16,7, GSM1: -> AT
2010-05-30 19:42:16,7, GSM1: Command is sent, waiting for the answer
2010-05-30 19:42:16,7, GSM1: <- AT OK
2010-05-30 19:42:16,6, GSM1: Initializing modem
2010-05-30 19:42:16,7, GSM1: -> ATE1+CMEE=1
2010-05-30 19:42:16,7, GSM1: Command is sent, waiting for the answer
2010-05-30 19:42:17,7, GSM1: <- ATE1+CMEE=1 OK
2010-05-30 19:42:17,6, GSM1: Checking if Modem is registered to the network
2010-05-30 19:42:17,7, GSM1: -> AT+CREG?
2010-05-30 19:42:17,7, GSM1: Command is sent, waiting for the answer
2010-05-30 19:42:17,7, GSM1: <- AT+CREG? +CREG: 2,1, 9D6D, 1930BBB OK
2010-05-30 19:42:17,6, GSM1: Modem is registered to the network
2010-05-30 19:42:17,6, GSM1: Selecting PDU mode
2010-05-30 19:42:17,7, GSM1: -> AT+CMGF=0
2010-05-30 19:42:17,7, GSM1: Command is sent, waiting for the answer
2010-05-30 19:42:17,7, GSM1: <- AT+CMGF=0 OK
2010-05-30 19:42:17,7, GSM1: -> AT+CMGS=18
2010-05-30 19:42:17,7, GSM1: Command is sent, waiting for the answer
2010-05-30 19:42:17,7, GSM1: <- AT+CMGS=18 >
2010-05-30 19:42:17,7, GSM1: -> 0011000A9154040383730000FF05E8329BFD06
2010-05-30 19:42:17,7, GSM1: Command is sent, waiting for the answer
2010-05-30 19:42:18,7, GSM1: <- 0011000A9154040383730000FF05E8329BFD06 +CMS ERROR: 330
2010-05-30 19:42:18,7, GSM1: Explanation: SMSC address unknown
2010-05-30 19:42:18,3, GSM1: The modem said ERROR or did not answer.
2010-05-30 19:42:18,5, GSM1: Waiting 10 sec. before retrying

The PDU is echoed back correctly, so this is not a communication problem.

When you tried to set the smsc, and got an error, what was that error? Or was it just an "ERROR"?

Do you have another SIM card, and can you try the sending with it, without setting any smsc?

I upgraded to Fedora 13 (completely new installation) and to SMS Server Tools 3.1.5 (included i this distribution as standard) and now everything works perfectly

The problem I had was clearly related to my fedora 12 installation and configuration which I suspected.

cookman wrote

I upgraded to Fedora 13 (completely new installation) and to SMS Server Tools 3.1.5 (included i this distribution as standard) and now everything works perfectly

The problem I had was clearly related to my fedora 12 installation and configuration which I suspected.

Ok, thanks for the information.

I still do not understand what went wrong with Fedora 12. The code for sending the data is the same, as you have not changed send_delay to 0. Anyways, good that it works now.