<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div><br>
I noticed how you mentioned asterisk and if it could handle that many calls and you seemed skeptical. Probably based on experience. After all these years I thought a single asterisk server could handle more calls in a stable fashion but it appears not. Once
past 500 concurrent calls, depending on hardware and config, things start to get sketchy. It has been a while since I last used asterisk for a VM server or pbx. Those days seem long ago.<br>
<br>
Over the years we have had customers experience TDOS. While we have no current customer experiencing the issue today we wanted to research our options just in case.<br>
<br>
It seems metaswitch has a cloud based robocall blocking feature we just read about. I have to wonder if that hook in the switch could be used for something.<br>
<br>
As others have said though... gathering all this cdr info, analyzing it, and then blocking certain calls while keeping good ones is quite the task to program. And to do it really fast. One can stop trivial attacks that have a pattern but a determined attacker
can be quite crafty.<br>
<br>
Thank you everyone,<br>
<br>
Matt
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> sasha@evaristesys.com <sasha@evaristesys.com> on behalf of Alex Balashov <abalashov@evaristesys.com><br>
<b>Sent:</b> Tuesday, May 16, 2017 5:01:04 PM<br>
<b>To:</b> Matthew Yaklin<br>
<b>Cc:</b> voiceops@voiceops.org<br>
<b>Subject:</b> Re: [VoiceOps] Mitigating or stopping TDOS attacks - any advice?</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">A "voice CAPTCHA" is a viable solution. But it does require<br>
infrastructure commitments on your part, even if, as you say, an<br>
Asterisk box can handle many concurrent calls. If you want to recycle<br>
that across multiple customers, that kind of moat can get mildly<br>
complicated.<br>
<br>
The only concern I would have is from a user experience point of view;<br>
your customer might not want their callers to have to go through a<br>
confusing menu, and it would doubtless be psychologically off-putting.<br>
I don't know what kind of business the customer is, but imagine if you<br>
called your dentist's office and were prompted to enter some sort of<br>
PIN. As a layperson, you might think something is wrong with the phone<br>
system.<br>
<br>
-- <br>
Alex Balashov | Principal | Evariste Systems LLC<br>
<br>
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) <br>
Web: <a href="http://www.evaristesys.com/">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/">
http://www.csrpswitch.com/</a><br>
</div>
</span></font>
</body>
</html>