nanog mailing list archives

Re: OffTopic: Telecom Fraud


From: Mel Beckman <mel () beckman org>
Date: Tue, 23 Apr 2019 20:58:12 +0000

From the NANOG mailing list FAQ:

“You can help keep NANOG's signal-to-noise ratio high by subscribing to the nanog-offtopic () lists blank 
org<mailto:nanog-offtopic () lists blank org> list, and migrating digressive conversations there. To subscribe, send 
mail to nanog-offtopic-subscribe () lists blank org<mailto:nanog-offtopic-subscribe () lists blank org> and reply to 
the confirm message it will generate.”

-mel via cell

On Apr 23, 2019, at 1:53 PM, Mel Beckman <mel () beckman org<mailto:mel () beckman org>> wrote:

Dovid,

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.

-mel beckman

On Apr 23, 2019, at 1:24 PM, Dovid Bender <dovid () telecurve com<mailto:dovid () telecurve com>> wrote:



On Tue, Apr 23, 2019 at 4:18 PM Paul Timmins <paul () telcodata us<mailto:paul () telcodata us>> wrote:
I guarantee you that if carriers were made civilly or criminally liable
for allowing robodialers to operate on their network, this sort of issue
would end practically overnight. Robodialer calling patterns are
obvious, and I'd imagine any tech could give you a criteria to search
for in the CDR streams to identify them and shut them off in hours.

Problem is, they're lucrative to provide services to, and there is
immunity on the carrier's part to these sorts of issues. SHAKEN/STIR
nonwithstanding (I don't think we'll see widespread adoption of this
within a decade, even with a government mandate as there's still a
massive embedded base of switches that can't support it and never will).

It may be incredibly frustrating, but there's plenty of money to be made
in prolonging the problem.


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 https://www.multichannel.com/news/comcast-and-att-test-anti-robocalling-tech 
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.



Current thread: