The FCC adopted additional robocall mitigation rules in triggering certain compliance deadlines.
The order requires all providers to implement the FCC’s general robocall mitigation standard and to submit a robocall mitigation plan in the Robocall Mitigation Database (RMD), even if the provider has fully implemented STIR/SHAKEN. It expands the information that must be submitted in the robocall mitigation plan and requires the first intermediate provider in the call chain to authenticate unsigned SIP calls received directly from the originating provider. You can find out the details here.