FCC compliance for carriers
The FCC robocall compliance guide.
What a voice service provider actually has to do to stay compliant — RMD certifications, STIR/SHAKEN, blocking, traceback, KYC — and what happens if it doesn't.
Core obligations
The obligations that matter most
- 01
Keep an accurate RMD certification
Providers handling U.S. traffic — domestic or foreign, originating, intermediate or gateway — need a current certification in the Robocall Mitigation Database that describes real KYC, monitoring and traceback practices.
- 02
Authenticate calls with STIR/SHAKEN
If any part of your network carries calls over IP, those calls should be signed. Extensions have largely ended and reliance on others to sign is more restricted than it used to be.
- 03
Block based on reasonable analytics
Providers must take effective steps against illegal traffic and act when notified of it by the FCC or industry traceback. Failing to act after notice is a fast route to enforcement.
- 04
Answer traceback within 24 hours
Respond fully to Industry Traceback Group requests promptly. Ignored or late tracebacks are routinely cited in FCC enforcement actions.
- 05
Know your customers — and upstreams
Vet who sends you traffic, keep records, and apply extra scrutiny to high-volume callers. Expectations here are growing.
- 06
Understand the Section 214 risk
The FCC can revoke operating authority from carriers with serious robocall violations, ending their ability to operate as common carriers in the U.S.
How VoIP Radar helps
Each requirement, covered
RMD plan templates
Plan language that reflects modern expectations around KYC, monitoring and traceback — customized to what you run.
Signing & verification
STIR/SHAKEN at your SBC, with attestation driven by real KYC data.
Analytics-based blocking
Real-time scoring stops highly likely illegal calls before they leave your network.
Traceback automation
Traceback requests matched to call records so you can respond fully inside 24 hours.
Continuous KYC
Ongoing customer and upstream re-verification, not a one-time onboarding form.
Enforcement-ready records
Every decision logged with attestation, score, KYC status and traceback history.
Quick reference
Key rules and frameworks voice providers should know. This is an overview, not legal advice.
| Requirement | What it covers | Where it comes from |
|---|---|---|
| STIR/SHAKEN | Caller ID authentication on IP networks | TRACED Act; 47 CFR Part 64, Subpart HH |
| RMD certification | STIR/SHAKEN status, mitigation plan, contacts | 47 CFR § 64.6305 |
| Call blocking | Blocking illegal and highly likely illegal traffic | 47 CFR § 64.1200(k) and (n) |
| Traceback | Responding to traceback requests promptly | FCC rules; ITG process |
| Caller ID integrity | No spoofing with intent to defraud or harm | Truth in Caller ID Act |
| Telemarketing & consent | Autodialed and prerecorded / AI-voice calls | TCPA |
Get in touch
Find out where your network stands
Tell us about your switch and traffic. A VoIP Radar engineer will map your STIR/SHAKEN, RMD and fraud exposure and send a written assessment — free, within one business day.
- STIR/SHAKEN & attestation review
- RMD certification gap check
- Fraud & robocall exposure snapshot
- Deployment plan for your SBC / softswitch