Operating system name and version: Windows XP SP3
Version of smsd: 3.1.14
Smsd installed from: sources
Name and model of a modem / phone: Siemens MC 35
Interface: serial

I have found new issue after upgrading to smsd 3.1.14 from 3.0.10.
I have modem with zero-balance sim in it.
When I try to send sms via the modem, eventhandler is called with SENT argument. This means that smsd assumes message as sent successfully. But indeed sms is not sent. Just after this event , sms notification is received by the modem from GSM Provider about zero balance : "An SMS you tried to send or receive has failed as you are out of credit for that message type. Recharge now to allow future SMS messages to be sent or received."

Please see log below
2011-02-08 21:50:42,6, M2: I have to send 1 short message for /var/spool/sms/checked/send_xu2640 2011-02-08 21:50:42,6, M2: Sending SMS from to 79262722716 2011-02-08 21:50:42,6, M2: Checking if modem is ready 2011-02-08 21:50:42,7, M2: -> AT 2011-02-08 21:50:42,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:43,7, M2: <- OK 2011-02-08 21:50:43,6, M2: Pre-initializing modem 2011-02-08 21:50:43,7, M2: -> ATE0+CMEE=1;+CREG=2 2011-02-08 21:50:43,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:43,7, M2: <- OK 2011-02-08 21:50:44,7, M2: -> AT+CSQ 2011-02-08 21:50:44,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:44,7, M2: <- +CSQ: 19,99 OK 2011-02-08 21:50:44,6, M2: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable 2011-02-08 21:50:44,6, M2: Checking if Modem is registered to the network 2011-02-08 21:50:44,7, M2: -> AT+CREG? 2011-02-08 21:50:44,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:45,7, M2: <- +CREG: 2,1,"0B68","3A37" OK 2011-02-08 21:50:45,6, M2: Modem is registered to the network 2011-02-08 21:50:45,6, M2: Location area code: 0B68, Cell ID: 3A37 2011-02-08 21:50:45,7, M2: -> AT+CSQ 2011-02-08 21:50:45,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:45,7, M2: <- +CSQ: 19,99 OK 2011-02-08 21:50:45,6, M2: Signal Strength Indicator: (19,99) -75 dBm (Good), Bit Error Rate: not known or not detectable 2011-02-08 21:50:45,6, M2: Selecting PDU mode 2011-02-08 21:50:45,7, M2: -> AT+CMGF=0 2011-02-08 21:50:45,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:46,7, M2: <- OK 2011-02-08 21:50:46,7, M2: -> AT+CMGS=19 2011-02-08 21:50:46,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:46,7, M2: <- > 2011-02-08 21:50:47,7, M2: -> 0011000B919762722217F60000C405C82293F904. 2011-02-08 21:50:47,7, M2: Command is sent, waiting for the answer 2011-02-08 21:50:50,7, M2: <- +CMGS: 25 OK 2011-02-08 21:50:50,5, M2: SMS sent, Message_id: 25, To: 79262722716, sending time 8 sec. 2011-02-08 21:50:50,7, M2: Running eventhandler: /usr/src/myscripts/centaur_sms_20090205.sh SENT /var/spool/sms/checked/send_xu2640 25 2011-02-08 21:50:51,7, M2: Done: eventhandler, execution time 1 sec., status: 0 (0) 2011-02-08 21:50:51,6, M2: Deleted file /var/spool/sms/checked/send_xu2640

I see such issue for the first time.
Any advice?!

There is no difference between 3.0.10 and later versions in this case.

SMS was delivered to the Service Center and smsd got a reference number for it, in your case 25. Service Center did not tell that it cannot deliver SMS to the recipient, instead it told that the sending was OK. Some other operators may give an error message in that kind of case, like "Short message transfer rejected", or something else, but it depends on the operator.

You could try to use the modem setting report = yes, together with the global setting sent = /var/spool/sms/sent and the script smstools3/scripts/eventhandler_report. I assume that when SMSC will not deliver message, it also does not return a status report which says that the SMS is delivered to the phone. You can use this information to detect which messages are delivered and which are not, after message about zero balance is received.

See also this topic: Sample config and script for regular_run and balance of prepaid SIM using USSD, it may be very useful in your system.

Keke, thanks again!

Most of our modems use non prepaid sims. Because of this I see the issue for the first time.
Will think of possible solution.

Thank you for the link

Okay, if the invoice of postpaid SIM is not paid, and SIM is closed, you may get the "+CMS ERROR: 302 (Operation not allowed)". This is stored to the failed SMS file as a Fail_reason. Also an alarmhandler is called, and alarmhandler could generate some alert if this kind of error is shown.