Re: [VoiceOps] Robocall Mitigation in lieu of STIR/SHAKEN

[paul]

I'm guessing I'll use some CDR analysis on our TDM switch to look for customers sending numbers they don't own on caller ID, and just make a report and build exceptions in a table for stuff we allow. It would ideally over time just come down to a handful of anomalies. Most of our customers send their own numbers or a toll-free so a quick daily script should be adequate. If someone starts spoofing we'd get notified pretty fast. The SIP traffic has been signed for almost a year now. On Mar 9, 2021 19:30, "Zilk, David" <david.z...@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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops