[cisco-voip] Robo Call DoS

[Bill Talley]

I’m sure you’ve already considered this, but I wonder, with everything being back-hauled over IP these days, if their telco would be able to identify the IXC who is handing off the call to them, based on the logs for the original calling party number they blocked, and blacklist that address.  Sure that sounds extreme (voice is more critical them SMTP), but you’re also talking about criminal activity.

Sent from an iOS device with very tiny touchscreen input keys.  Please excude my typtos.

> On Apr 16, 2018, at 10:23 AM, Anthony Holloway <avholloway+cisco-voip at gmail.com> wrote:
> 
> Technically or legally?
> 
> How does one stop a DoS attack on a network?  Or on anything for that matter?  Say you were attending a protest, and someone is blowing an air horn in your ear?  What can you do?
> 
> Technically, you could front end the whole thing with a captcha style gate, so you could ask to push a single button, button combination, or solve a simple addition problem resulting in two digits.  granted, just like on the web, a captcha is burdensome to the user, but generally, it's preferable over the site being down, or disrupted.
> 
> CUC and UCCX both could handle this task, though it would be easier in UCCX.
> 
>> On Mon, Apr 16, 2018 at 9:49 AM Matthew Loraditch <MLoraditch at heliontechnologies.com> wrote:
>> So this is a curiosity question, we had a prospective client call us who is essentially getting robocalled to oblivion. Some scammer has robo dialers setup and is flooding all of their trunks. He got a ransom, stopped and then started again. He was originally using one number and then when the telco blocked that switching to random sources.
>> 
>> Are there are any legitimate defenses to this sort of thing?
>> 
>>  	
>> Matthew Loraditch​
>> Sr. Network Engineer
>> p: 443.541.1518
>> w: www.heliontechnologies.com	 | 	e: MLoraditch at heliontechnologies.com
>> 
>> 
>> 
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180416/3b3cd34e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image164818.png
Type: image/png
Size: 8404 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180416/3b3cd34e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image955318.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180416/3b3cd34e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image614350.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180416/3b3cd34e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image165691.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180416/3b3cd34e/attachment-0003.png>