Operating system name and version: Windows XP SP3
Version of smsd: 3.1.6
Smsd installed from: sources (cygwin)
Name and model of a modem / phone: Nokia 6102
Interface: serial / USB

I have a question, sometimes my smsd its working fine but then some of my modems get to the point when they are stuck at sending like:
GSM6 -> 0320BGF6738 (the whole pdu)
GSM6 Command is sent waiting for answer

And in there it can be like 10 or 15 minutes of inactivity is there a way to reset only that modem so it keeps sending sms

Thanks!

Currently it's not possible to restart only one modem process. You have to restart whole smsd using sms3 script.

When your modem stall, does the restarting of smsd help, or do you need to disconnect & reconnect the cable or perhaps switch off & on the modem?

While thinking the reason for stalling, have you never resent a failed message successfully? For example, some modems stall if a national number format is used instead of international number format.

If you show the complete PDU from some stalled message, I could check if there is anything wrong which may cause the problem. You can use Private tags to protect the PDU string. See this post for details.

( Or did you mean that "0320BGF6738" was the real and complete PDU? If so, something is wrong very badly... )

Thanks so much for the fast answer, and yeah restarting the service totally helps and makes every modem work just fine and NO i havent been able to resend any failed sms ever!

Original PDU of a stalled sms:

Hidden private text.

If i restart sms3 and some other modem is sending an sms will it fail and resend later or it will just not be sent?

Thanks so much!

With a quick view there is nothing wrong in the format of a PDU.

Generally taken, you could avoid to use linefeed on the end of a message. In this message it does not matter, but if you are sending exactly 160 visible characters, linefeed causes that an additional part is sent and it will increase costs.

michel wrote

...and NO i havent been able to resend any failed sms ever!

You have tried, right? Could it be possible that the number is incorrect or unused? In this kind of case SMSC should return an error code and modem should handle it, but probably it does not work and therefore a modem stall.

Do you have any other devices than Nokia 6102? If you have, you could try resending with a different device.

michel wrote

If i restart sms3 and some other modem is sending an sms will it fail and resend later or it will just not be sent?

When smsd is stopped using the sms3 script, all processes will get a terminate request. This is not the same as kill. All modems will finalize the job which was started but not yet completed. Sending is not interrupted, even with messages with multiple parts (messages with more than 160 characters). After a message is sent, no more messages are picked up and the modem process will stop. After all modem processes are stopped, the main process will stop, and right after that the sms3 script will start everything again.

Thanks so much for the answers Keke

Ill fix the linefeed thing, thank you

I have to resend failed yeah, but actually they dont fail they just stall and i am working on a script to restart sms3 service

Right now i dont have any other devices i was planning on buying something like this: link
u think it would work fine?? or do i stick to mobiles??

And one last question is there a way to start sms3 service like "sms3 start" but that has the -s argument to read the statistics on the shell window??

Thanks so much!

michel wrote

u think it would work fine?? or do i stick to mobiles??

If it supports SMS command set according to the european specification GSM 07.05 (=ETSI TS 300 585), a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode") of it, and alphabet support according to the GSM 03.38 (=ETSI TS 100 900), it may work. I have not checked this device.

Some of those kind of devices are reported as working, like Huawei E169. However, real modems are usually better by stability.

michel wrote

And one last question is there a way to start sms3 service like "sms3 start" but that has the -s argument to read the statistics on the shell window??

There is no such kind of argument, but it can be easily added if necessary: $DAEMON $ARGS $2. The script does not have it by default, because it's often called by the OS and there is no console available.

As you have compiled smsd with status monitor, you could enable monitoring and smart logging:


With this kind of settings, you can use the following script for monitoring. It's much better than just the output from -s.



You may need to change directories, but hopefully this script is useful for you, at least as an example.