[VoiceOps] Robocall Mitigation in lieu of STIR/SHAKEN

[Calvin Ellison]

For those doing CDR analysis, the Industry Traceback Group held a
webinar in November that provided some suggestions.

The full presentation is here:
https://www.ustelecom.org/preventing-illegal-robocalls-know-the-rules-know-your-customer-and-know-your-traffic/

PDF:
https://www.ustelecom.org/wp-content/uploads/2020/11/Mitigating-Robocalls-Best-Practices-Presentation-November-2020.pdf

Key metrics to watch:
• Average Call Duration (calls shorter than 6, 18, 30, 60 seconds)
• Trends in daily call volume
• Answer Seizure Ratio (fraction of calls answered)
• Unique Caller-ID values (ratio of total calls to unique CLID’s)


Regards,

Calvin Ellison
Systems Architect
calvin.ellison at voxox.com



Regards,

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

-----------------------------------------------
voxox.com
5825 Oberlin Drive, Suite 5
San Diego, CA 92121




On Tue, Mar 9, 2021 at 6:57 PM <paul at timmins.net> wrote:
>
> 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.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