Source note · Robocall mitigation and RMD obligations
A provider may certify complete or partial implementation in the Robocall Mitigation Database only if it has obtained an SPC token and digital certificate and signs calls with its own certificate.
Checked 2026-09-16
- Vendor
- Federal Communications Commission
- Product
- Robocall Mitigation Database
- Subsystem
- certification content
- Deployment
- all-us-voice-service-provider-networks
- Region
- united states
- Release range
- compliance from 2025-09-18
- Checked
- 2026-09-16
Sources
- Call Authentication Trust Anchor, Eighth Report and Order (FCC 24-120) — Federal Communications Commission · tier 1 standards and regulators · FCC 24-120 para 27
Cite this note
APA
WarmTransfer. (2026, September 16). Robocall mitigation and RMD obligations: source note robocall-mitigation-cert-requires-own-certificate. WarmTransfer. https://warmtransfer.net/knowledge/claims/robocall-mitigation-cert-requires-own-certificate
BibTeX
@misc{warmtransfer-claim-robocall-mitigation-cert-requires-own-certificate,
title = {Robocall mitigation and RMD obligations: source note robocall-mitigation-cert-requires-own-certificate},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/robocall-mitigation-cert-requires-own-certificate},
note = {Source note robocall-mitigation-cert-requires-own-certificate, checked 2026-09-16}
}