| BlackList nember |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 113 Registered: 04-2011 |
Hi, We are submitting messages to NowSMS over HTTP. We also use the SMSCRoute parameter to address the route for the message. However, we would like to drop some number patterns (for e.g. landline numbers having pattern +9744*). Do advise as to how do we can go about this. Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5787 Registered: 08-2008 |
Hi Mathew, Are you currently using accounting callbacks? I'm just wondering how the SMSCRoute is being set, so that I can answer with a solution appropriate for your environment. -- Des NowSMS Support | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 114 Registered: 04-2011 |
Hi Yes.. We are using the accounting callbacks also.... for logging. SMSCRoute is a part of the HTTP request message while submitting the message. These requests are submitted by several applications and if a blacklist setting is available, we could control these from a single point without any application level changes. Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5791 Registered: 08-2008 |
Hi Mathew, If your accounting callback can process SMSSend PreAuth=Yes requests and issue the following response when a blacklist number is encountered, the messages will be rejected: PreAuth=Deny SMPPErrorCode=0x0B RejectText=Blacklisted number SMPPErrorCode only applies if you are accepting SMPP submissions. 0x0B is the error code for invalid destination. RejectText only applies for HTTP submissions. This text appears in the HTTP response to make troubleshooting easier. Note that the above response causes your system to reject the message and return an error to the submitting client. You might prefer to accept the message, but silently discard it. This is possible, but is sort of a hack. Let me explain. The easiest way to have the system silently discard a message is to create a fake HTTP SMSC connection. Configure NowSMS with an HTTP SMSC connection to a web server that is going to ignore your request. Assuming you give this connection a route name of Blacklist, your accounting callback can override the SMSCRoute by returning SMSCRoute=Blacklist in the HTTP response. -- Des NowSMS Support | |||
| Mathew Mathachan Frequent Contributor Username: Mathewm Post Number: 115 Registered: 04-2011 |
Hi, We do have a BlackHole HTTP host to direct all unwanted messages. I was looking at giving a wild card configuration on Gateway. Thanks Des Looks like handling it on PreAuth callbacks is the only option. Thanks for the support Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5792 Registered: 08-2008 |
Hi Mathew. If you use the SMSCRoute on submission, this overrides any prefix/wildcard routing. -- Des NowSMS Support | |||
