FCC Removes 1200 VoIP Providers from Robocall Mitigation Database

[MichaelB_3CX]

3CX is not affected by these actions but your non-compliant SIP trunk provider may be!​

August 2025, the Federal Communications Commission (FCC) announced the removal of more than 1200 VoIP providers from its Robocall Mitigation Database (RMD). These providers were found to have unresolved deficiencies in their certification filings. Th...

Continue reading the Original Blog Post.

 

[pmterp]

First, I'd like to say thank you for sharing this information. While I know it does not directly impact 3CX, it is great to share this information here to ensure people are aware of the impact of this.
Does 3CX have any plans for implementing STIR/SHAKEN tools within the system? Certificate signing or even inbound handling based on attestation would be great tools to have within 3CX as opposed to using outside resources.

 

[N_G]

No, your provider has to do this.

 

[pmterp]

No, your provider has to do this.

Understood. I was hoping for something more granular, especially on the inbound side of things. If the provider passes the attestation level, we'd love the ability to prepend an identifier or route the call differently. For example, if the attestation is "A", we pass the call along but if it's a "C", we force the caller through an IVR.