| SMS DoS Attacks |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| michael lumpp New member Username: Tek7 Post Number: 1 Registered: 08-2007 |
Hello all, I am considering an evaluation of NowSMS and was curious to know how DoS attacks are handled - in particular not so much as to say how to mitigate issues from the gateway sending data to the webserver, but rather what to do in the event that too many messages are sent from devices/webpages/etc TO the gateway itself. Is there a way to limit what is sent from the same number, or anything else clever? How about pre-processing a message that comes in so the gateway takes no action on it (doesn't go through the gateway), rather through some sort of script or something of that nature. Thanks for your help, Mike | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7472 Registered: 10-2002 |
Hi Mike, The Pre-Auth SMS accounting callback could be implemented on your end to add this type of tracking/detection. http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm The link above needs to be updated, as for quite some time the pre-auth callback has included a "To=" parameter for recipient information, as well as "Text", "Data", "PID", "DCS" and "UDH" information. -bn | |||
