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

2021-03-09 Thread 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

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

2021-03-09 Thread 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

[VoiceOps] Robocall Mitigation in lieu of STIR/SHAKEN

2021-03-09 Thread Zilk, David
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