<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
From the NANOG mailing list FAQ:
<div><br>
</div>
<div>“<span style="background-color: rgba(255, 255, 255, 0);">You can help keep NANOG's signal-to-noise ratio high by subscribing to the <a href="mailto:nanog-offtopic@lists.blank.org" style="text-decoration: none; font-style: italic;">nanog-offtopic@lists.blank.org</a> list,
and migrating digressive conversations there. To subscribe, send mail to <a href="mailto:nanog-offtopic-subscribe@lists.blank.org" style="text-decoration: none; font-style: italic;">nanog-offtopic-subscribe@lists.blank.org</a> and reply to the confirm message
it will generate.”</span><br>
<br>
<div id="AppleMailSignature" dir="ltr">-mel via cell</div>
<div dir="ltr"><br>
On Apr 23, 2019, at 1:53 PM, Mel Beckman <<a href="mailto:mel@beckman.org">mel@beckman.org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">Dovid,
<div><br>
</div>
<div>You are correct that your message is off topic. I respectfully ask that you honor the rules of this mailing list and refrain from off topic posts. They simply add noise to an otherwise useful and highly germane experts resource. <br>
<br>
<div dir="ltr">-mel beckman </div>
<div dir="ltr"><br>
On Apr 23, 2019, at 1:24 PM, Dovid Bender <<a href="mailto:dovid@telecurve.com">dovid@telecurve.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Apr 23, 2019 at 4:18 PM Paul Timmins <<a href="mailto:paul@telcodata.us">paul@telcodata.us</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I guarantee you that if carriers were made civilly or criminally liable <br>
for allowing robodialers to operate on their network, this sort of issue <br>
would end practically overnight. Robodialer calling patterns are <br>
obvious, and I'd imagine any tech could give you a criteria to search <br>
for in the CDR streams to identify them and shut them off in hours.<br>
<br>
Problem is, they're lucrative to provide services to, and there is <br>
immunity on the carrier's part to these sorts of issues. SHAKEN/STIR <br>
nonwithstanding (I don't think we'll see widespread adoption of this <br>
within a decade, even with a government mandate as there's still a <br>
massive embedded base of switches that can't support it and never will).<br>
<br>
It may be incredibly frustrating, but there's plenty of money to be made <br>
in prolonging the problem.<br>
<br>
</blockquote>
<div><br>
</div>
<div>That was my thought as well. From what I heard last 50% of the calls are fraud. That's a lot of money that they are collecting on origination. I also saw this <a href="https://www.multichannel.com/news/comcast-and-att-test-anti-robocalling-tech">https://www.multichannel.com/news/comcast-and-att-test-anti-robocalling-tech</a> and
did a test. A client owned a Comcast number and had ATT. I set the CLI to the Comcast number and it showed up on the ATT phone as I set it. You would think if ATT had the tools in place at the very least it wouldn't display the number.</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</body>
</html>