| SMS and MMS failure to deliver notifications |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Lite Support ⬆ Archive through September 20, 2012 ⬆ |
◄ ► |
| Author | Message | |||
| Neil Stamps New member Username: Neil Post Number: 48 Registered: 12-2009 |
We have an application that expects to have delivery notifications, and that is working ok. What we would like to test is the failure to deliver notifications. Is there any way to force the gateway to give failed to deliver notifications for SMS and MMS, for example is it possible to set some sort of timeout or retry to be very low so that if an incorrect number was used, or the modem was not plugged in it would quickly respond with a failure callback. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2012 Registered: 08-2008 |
Hi Neil, If the modem is not plugged in, we do not error out the message. This is considered to be a connection failure. The only way to monitor connection failures of this sort is to use the status query interface: http://blog.nowsms.com/2009/02/xml-status-query-for-smsc-connection.html Regarding invalid numbers ... behaviour can vary by operator. Some operators will accept the message, but later return a non-delivery report (or no delivery report at all), others will reject the message on submission. The following article has details on configuring retry parameters: http://blog.nowsms.com/2008/10/sms-retry-error-handling-with-ucpemi.html This article talks mainly about other types of SMSC connections, not modems ... however it does cover the general error handling settings with regard to retries. -- Des NowSMS Support -- Des NowSMS Support | |||
