[VoiceOps] Robocall Mitigation in lieu of STIR/SHAKEN

[Calvin Ellison]

You may want to consider integrating with a reputation service provider
that provides A) real-time data, and B) works closely with the Industry
Traceback Group to identify the real problem traffic, rather than the
"legal nuisance" traffic. This is a non-apologetic name drop for *YouMail*,
but other names out there are TrueCNAM, Robokiller, First Orion, Hiya,
Nomorobo. If you are looking for a drop-in solution, TransNexus ClearIP
or NexOSS may work for you.

We chose to roll our own using OpenSIPS and localized data sources with
caching to keep latency low. I'd be happy to discuss this further but can't
reveal the 11 herbs and spices or the way we prepare the special sauce.


Regards,

*Calvin Ellison*
Systems Architect
calvin.ellison at voxox.com
+1 (213) 285-0555

-----------------------------------------------
*voxox.com <http://www.voxox.com/> *
5825 Oberlin Drive, Suite 5
San Diego, CA 92121
[image: Voxox]


On Tue, Mar 9, 2021 at 5:22 PM Alex Balashov <abalashov at evaristesys.com>
wrote:

> Well, a number of bright-eyed, bushy-tailed, enterprising eager beavers
> have ploughed full-on into the dubious business — more superstition than
> science — of proprietary reputation-scoring / spam risk-scoring for
> numbers. Nothing more exciting to the entrepreneurial element than an
> opportunity to provide a knock-off of a regulatory requirement that falls
> just a millimetre shy of overt intellectually fraud.
>
> I imagine querying one of those services’ database of numbers scraped from
> the National Association of Ignoble Car Warranty Merchants or Ashley
> Madison or whatever ... could be construed to the gullible as a
> “good”-faith effort at robocall mitigation. It’s an A-for-effort kind of
> cultural moment anyhow.
>
> —
> Sent from mobile, with due apologies for brevity and errors.
>
> On Mar 9, 2021, at 7:32 PM, Zilk, David <David.Zilk at cdk.com> wrote:
>
> 
>
>
>
> The FCC is mandating that service providers must fully implement
> STIR/SHAKEN or certify that they are taking reasonable steps to avoid
> originating illegal robocall traffic in the portions of their network where
> STIR/SHAKEN can’t be implemented. They have also declined to specify what
> those steps might be, though there may be more information available when
> they clarify the certification process by March 30th.
>
>
>
> What steps are people taking to meet this robocall mitigation requirement
> when STIR/SHAKEN is not able to be implemented?
>
>
>
> David
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20210309/a3da3724/attachment.htm>