| PreAuth Call back |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 20, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| Mathew Mathachan New member Username: Mathewm Post Number: 37 Registered: 04-2011 |
We wanted to maintain a white list of numbers where by any SMS to numbers outside of the list is dropped. We are submitting the request to SMSGateway over HTTP. We planned to do this in the Preauth call back to lookup the white list and allow/deny. We setup the tag SMSAccountingPreAuthPerRecip in the SMSGW.INI, so that individual PreAuth callbacks are received for submissions with multiple GSM numbers. Now we see that, when an HTTP Submit request is made with multiple GSM numbers and one of the PreAuth callback is denied, we get HTTP Submit response as Status Code 403. Also we see that none of the messages that have been allowed/authorised are sent (NO SMSSEND callback generated). Infact, if any one of the PreAuth callbacks are denied, all of the messages are dropped. Appreciate your support/advise on this situation. Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4306 Registered: 08-2008 |
Hi Mathew, Yes, that is how the PreAuth works. PreAuth=Deny is a signal that the message is to be rejected. Unfortunately if a message has multiple recipients, the entire message must be rejected. The only alternative I can think of would be to setup a dummy route, and instead of rejecting the recipients, route them to this dummy route. (The dummy route can be an HTTP SMSC pointing to any web server which will just ignore the URL parameters.) -- Des NowSMS Support | |||
