Operating system name and version: centos 5.4
Version of smsd: smstools-3.1.14-1.x86_64
Smsd installed from: package repository
Name and model of a modem / phone: two Huawei modems
Interface: USB

Hello all

The default behaviour of smsd when a modem returns a 500 ERROR is to retry, and then to give up moving the message to the failed directory. You can initiate another round by moving it to the outgoing dir again, or run a script that does that for you.

That seems good, but I noticed that, even having 2 modems, the re-try almost all the time is on the same modem that it originaly tried. Is this configureable? I would like it to try the next modem when one fails. I changed the number of retries to 3, now it tries a little more, and sometimes seems to pick the other modem, but still most of the time stick to the original one.

The problem is that the accounts I'm using are pre-paid, and some times they run out-of-credits and it takes a little time for us to notice. I also (for stupid reasons) cannot put a lot of credit on them and forget. So I have two modems, even not really needing more than one, that will not normally expire at the same time.

It does not help to have two modems and still have a message to stick retrying to the out-of-credits modem and ultimately fail, even having a good modem on the system.

Can a "retry sequentially all the modems on the system" be implemented?

Thank you!
Andre

Bump. Anyone?

thanks!

Andre

Andre,

I know exactly what you mean because I had used another SMS gateway software that will retry on a different modem (automatically).
Talk to me: velhochico2012@yahoo.com.br

Aguardo seu e-mail mano!

Any solution to this? Would be great if you could publish your private solution

schindld, I guess Andre didn't find a solution yet. I've e-mailed him in private and he seems to be stucked yet.

Maybe we should modify the source code a little bit to move on the retries to another modems.

I think this would be a good feture request. I will post it there

No, I have not yet found a solution for this. In fact, I was hoping that this could be achieved just by proper configuration (something simple that I just overlooked).

What velhochico and I discussed was that the feature was available on other software, not a specific solution to this.

I wonder if keke could give us his valuable opinion on the problem.

In any case this is an external feature of smsd's point of view. When sending fails, eventhandler is called with FAILED status. That external script should take care of re-sending, and handle reasons for failures. It should check what queue was used, and select the next queue, and place the message back to the spooler. And after couple of tries, it should permanently stop re-trying.

This kind of functionality was discussed in the past, but while being mobile, I'm unable to search and browse topics. I think that some sample can be found, but probably it does not do the job as exactly wanted, because there are different needs in different systems.

Hi keke!!

Thank you for the fedback.

I understand the proposition, and I think it is doable. In fact, I already have a event handler taking care of other things, including flagging failed messages in a database, so I guess it would not be much work to implement that extra step before giving up.

But I think smsd is so close to doing that that it could be (IMHO) easy to implement and make peoples lives easier from the start. It already has inteligence to select a modem and to retry a number of times, even the number of times is configurable, it seems logical to have an option to make it's next re-try to be on a different modem (no need to be fancy, just exclude the current and pick again).

Thanks again!