AVB Veritas

Case study · FCC robocall compliance · 2024

Robocall Mitigation and Traceback Readiness

In September 2024, RGTN USA filed in the FCC Robocall Mitigation Database and submitted a mitigation plan under 47 C.F.R. section 64.6305. Leonardus Herps served as the responsible officer and robocall-mitigation contact. The program connected customer vetting, number validation, traffic monitoring, traceback cooperation and enforcement escalation.

The filed framework

  • Commitment to respond fully to traceback requests within 24 hours
  • Cooperation with the FCC, law enforcement and the industry traceback consortium
  • Customer identity and business-purpose vetting before service activation
  • Contractual restrictions against illegal robocalling and cooperation duties across interconnected providers
  • Validation of a customer’s right to use calling numbers
  • Recurring review of call-detail records and suspicious traffic patterns
  • Escalation options including investigation, suspension, termination and notification to authorities

Herps’s role

The FCC database record identifies Leonardus Herps as CEO, responsible contact and officer certifying the filing. This placed executive accountability directly behind the program’s commitments.

Why traceback readiness is complex

A useful response requires more than finding a customer name. The provider must correlate timestamps, calling and called numbers, Call-ID and routing records; identify the immediate upstream or originating source; preserve evidence; respond within the required window; and take action without disrupting legitimate traffic unnecessarily.

Risk-based controls

The filed plan described attention to unusual traffic volume, short-duration or low-completion calling, sequential dialing, calls to invalid or do-not-call numbers and traffic involving unassigned numbering ranges. These indicators require context and investigation rather than automatic assumptions of wrongdoing.

Expertise demonstrated

The work combines STIR/SHAKEN, numbering validation, CDR analysis, carrier interconnection, customer due diligence, fraud controls and regulator-facing evidence. It provides a foundation for analyzing how illegal traffic entered a network, which party controlled the relevant step and whether preventive or responsive controls were reasonable.

Security discipline

This public summary does not reproduce network architecture, vendor details, internal interfaces, customer data, authentication material or operational playbooks. Filing a plan establishes stated controls and commitments; it does not prove that no later incident can occur.

Questions from instructing counsel

Frequently asked questions

Who was responsible for RGTN USA’s robocall-mitigation filing?

The FCC database record identifies Leonardus Herps as CEO, mitigation contact and certifying officer.

What did the program cover?

It covered traceback response, customer vetting, acceptable-use controls, number validation, traffic monitoring, investigation and escalation.

What is the traceback commitment?

The filing commits to full responses within 24 hours and cooperation with the FCC, law enforcement and the industry traceback consortium.

Does filing a mitigation plan guarantee that illegal traffic will never occur?

No. It documents controls and commitments. Effectiveness in a particular event must be tested against traffic records, response evidence and the facts of that event.

Public sources

FCC Robocall Mitigation Database↗FCC robocall mitigation requirements↗

For counsel

Discuss the technical record.

For conflicts and scope review, send the parties, jurisdiction or docket, issue and deadline. Do not send confidential case files until a secure transfer method is agreed.

Contact Leo Herps ↗