Apparently I'm not allowed to give things to the voip community any more. Locking.

For clarity: This is a free service provided by me (xrobau) and ClearlyIP. There was no 'official' service, so we made one for you!

You can call from any US number and it will read back to you what your calls Attestation level is, AND who is attesting it.

If the company who is attesting it is NOT who you are using for your phone service, they're doing it wrong - the FCC recently announced that effectively the company that bills the place that is dialing the number is the one that should be attesting the calls. (EG. if you're a VoIPXYZ customer and you call that number, and the call is NOT attested by VoIPXYZ, you need to tell them to fix it.)

The FCC aren't messing around! They recently sent this email to every registered carriage service provider who hadn't implemented STIR/SHAKEN:

Dear Robocall Mitigation Database Filer:

Based on FCC Form 477 Data, we believe you meet the Commission’s definition of a non-facilities based provider. Accordingly, we believe you were obligated to implement the STIR/SHAKEN caller ID authentication framework by June 30, 2022, and revise your filing in the Robocall Mitigation Database by July 15, 2022, indicating that you are no longer subject to an extension of the STIR/SHAKEN implementation requirement.

Per our review of that Database, you have not done so. We are sending this written notice to offer an opportunity for you to explain why you are not subject to the June 30, 2022, implementation deadline and to inform you that we will refer non-compliance to the Enforcement Bureau.

FCC rules 47 CFR §§ 64.6301(a) and 64.6304(a)(1)(i) require a non-facilities based small voice service provider to have fully implemented the STIR/SHAKEN caller ID authentication framework by June 30, 2022. FCC rule 47 CFR § 64.6305(b)(5) requires a voice service provider to update its Robocall Mitigation Database filing within 10 business days of any change to the information provided in its filing.

In the December 2021 Caller ID Authentication Fourth Report and Order, the Commission defined a voice service provider as “non-facilities based” if it offers voice service to end-users solely using connections that are not sold by the provider or its affiliates. See 47 CFR 64.6300(g), FCC 21-122, para. 19 (available at the following link: https://docs.fcc.gov/public/attachments/FCC-21-122A1.pdf).

The Commission explained that this definition tracked information collected in the FCC Form 477, and stated that it would use recent FCC Form 477 data to determine which Robocall Mitigation Database filers meet its definition of non-facilities based. Filers that have only reported interconnected VoIP subscriptions sold bundled with a transmission service carrying underlying VoIP service were deemed to fall within the Commission’s definition of “non-facilities based.”

Upon review of the FCC Form 477 data associated with the FCC registration Number you used to file in the Robocall Mitigation Database, we have determined that you meet the Commission’s identified criteria to be a “non-facilities based” small voice service provider that was required to have fully implemented STIR/SHAKEN by June 30, 2022 and to have updated its Robocall Mitigation Database filing accordingly. However, the Robocall Mitigation Database filing for which you are listed as the contact does not currently certify to complete implementation of the STIR/SHAKEN caller ID authentication framework pursuant to 47 CFR § 64.6301(a), nor does the filing identify any other extensions that are applicable.

By August 31, 2022, you must update your Robocall Mitigation Database filing to correct the issue, or provide evidence that the current filing is sufficient (i.e., that you are not subject to this requirement). We will refer non-compliance to the FCC’s Enforcement Bureau, which may pursue an enforcement action as appropriate.