Guest
2013-01-23T06:52:07Z
Hi,

We are using the ActiveSMS Basic Console - SMS TAP Transport and it has worked quite well for 18 months. I am wondering if we can set the maximum number of times ActiveSMS will retry if it fails to send the SMS? I can see that we can set the retry delay after error, but nothing where I can set the max retries.

In the past few days we have had an interesting scenario arise. We were contacted by the telecoms provider to warn us that we had called the TAP service phone number ~ 100 times in the last 24 hours. Normally it would only be 1 call per day.

There were errors such as this (and also errors suggesting a connection error) in the event log :

Message: COM Exception raisedFunction: CHandset::PollLoop_TemporaryConnectionDescription: Comms Exception raisedFunction: CActiveSMSTapTransport::ConnectDescription: Write data failedHResult: -2147467259

I have investigated and it seems that the calls were connecting but failing to negotiate properly, or dropping out part way through. We have reset the modem, PC, fax (which shares the same phone line) and it is now working again. The fax was also failing during this period, so there may have been a problem with a dirty line / noise.

Cheers.

Ross


PS. I can see that it does have a maximum, because there has also been an error in the log :

Message: Too many repeated errors - Logging from this function temporarily disabledFunction: CHandset::PollLoop_TemporaryConnection



Support
2013-01-23T11:51:38Z
The message retry limit is 5.

However, if there error occurs whilst establishing the TAP connection then this limit will not come in to play.

I suspect the error has occurred before the message is transmit has been attempted, therefore the message is not seen to be at fault so will not be failed.
Guest
2013-01-23T22:08:03Z
Hi,

Thanks for the reply. As the modem is actually re-dialing the phone number 100 times, and we are being charged for 100 phone calls, what is telling the model to redial?

Presumably the modem is told to redial by the software? And presumably the software is redialing because it knows the message has not been sent?

Anyway, is there any way to mitigate this scenario?

Cheers.

Ross
Users browsing this topic