Operating system name and version: SLES10 SP3 64Bit
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: MTCBA-G2-EN2-ED-EU
Interface: LAN

Sometimes I get errors like following in the system; are these errors local errors or remote? If these errors are local what might be the right action?
I'm not sure what the reason might be, what I should do over the alarm handler (restart smsd?) and how it might be possible to prevent such errors?

2011-07-15 08:10:39,6, GSMLAN1: Checking if Modem is registered to the network
2011-07-15 08:10:39,7, GSMLAN1: -> AT+CREG?
2011-07-15 08:10:39,7, GSMLAN1: Command is sent, waiting for the answer
2011-07-15 08:10:39,7, GSMLAN1: <- +CREG: 2,1,"0741","8F49" OK
2011-07-15 08:10:39,6, GSMLAN1: Modem is registered to the network
2011-07-15 08:10:39,7, GSMLAN1: -> AT+CMGS=140
2011-07-15 08:10:39,7, GSMLAN1: Command is sent, waiting for the answer
2011-07-15 08:10:40,7, GSMLAN1: <- >
2011-07-15 08:10:40,7, GSMLAN1: -> 001..........<long line>
2011-07-15 08:10:40,7, GSMLAN1: Command is sent, waiting for the answer
2011-07-15 08:10:43,7, GSMLAN1: <- +CMS ERROR: 21 (Short message transfer rejected)
2011-07-15 08:10:43,3, GSMLAN1: The modem answer was not OK: +CMS ERROR: 21 (Short message transfer rejected)
2011-07-15 08:10:43,7, GSMLAN1: Running alarmhandler: /usr/hfg/script/root/smsalert.sh ALARM 2011-07-15 08:10:43 3 GSMLAN1 "The modem answer was not OK: +CMS ERROR: 21 (Short message transfer rejected)"
2011-07-15 08:10:44,7, GSMLAN1: Done: alarmhandler, execution time 1 sec., status: 0 (0)


Axel

When you have sent messages successfully in the past, have you never sent message successfully to the same number which now fails?

CMS 21 comes from the network, so it is remote error. But it can be caused by the local problem. To find out if there is something wrong in the message, show that "001....<long line>" here using Private tag to protect it. I can then check if it's okay or not.

Hi,

this system sents sms like short letters (but no spam) to changing customer numbers, so I cannot say if we ever sent succsessful messages to such failed numbers.
It's hard to find out, because I have to archive and check logfiles.

Hidden private text.

Axel

Thanks. The message data itself is correct, so the number must be unused. Restarting smsd will not help, which means that you can just store failed message files and manually check the reason, and probably update your database of numbers of customers. You can also use eventhandler and first argument "FAILED" for creating some log of failed numbers, if necessary.

OK, thanks a lot
cheers
Axel