https://docs.fcc.gov/public/attachments/DOC-408083A1.txt
OVER 2,400 VOICE SERVICE PROVIDERS FACE REMOVAL FOR FAILING TO COMPLY
WITH THE ROBOCALL MITIGATION DATABASE FILING REQUIREMENTS
FCC to Also Consider Stricter Filing Requirements to Increase Awareness
of Robocall Mitigation Responsibilities
WASHINGTON, December 10, 2024—The Federal Communications Commission
today announced new enforcement and rulemaking actions to stop bad
actors from facilitating nuisance and illegal robocalls. The FCC’s
Enforcement Bureau announced that 2,411 voice service providers failed
to properly file in the Robocall Mitigation Database and must show
cause why they should not be removed. Removal from the database means
other providers will be prohibited from accepting call traffic from
these providers. Also today, FCC Chairwoman Jessica Rosenworcel
proposed new rules to further tighten filing requirements for the
Robocall Mitigation Database (RMD) to better ensure widespread
compliance and heightened awareness of provider responsibilities to
protect consumers.
All voice service providers must file certification in the Robocall
Mitigation Database to demonstrate their level of STIR/SHAKEN
implementation, describe their robocall mitigation plans, and provide
other required information the Commission uses to monitor compliance
with our rules. Participation in U.S. phone networks comes with a
responsibility to actively mitigate the risk of scam traffic reaching
consumers.
...
Personal anecdote: in the last month, 0 calls have come through for me
that
(a) were not already in my contacts and
(b) were not robocalls
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)