The FCC issued the so-called Fourth Order on December 10, 2021, requiring certain smaller voice providers to implement STIR/SHAKEN caller ID authentication a whole year earlier. Instead of the date June 30, 2023, they set a new deadline of June 30, 2022.
This blog aims to assist anyone concerned about SS implementation and highlight the FCC’s required measures. Note: SS applies to United States VSPs only.
A New Deadline for Non-Facilities-Based Small Providers
The FCC accelerated the deadline for two types of small voice service providers to adopt STIR/SHAKEN:
(1) Non-facilities-based providers
(2) Small voice carriers that have failed to minimize suspicious unlawful robocalls will have 90 days to adopt STIR/SHAKEN if they do not immediately assess traffic and take actions to mitigate detected traffic.
The FCC’s decision to reduce the deadline concerned all small non-facilities-based voice services providers (100,000 or fewer voice service subscriber lines). Facilities-based small voice carriers are still eligible for a one-year extension until June 30, 2023.
This means that all OTT (Over the Top) service providers have a deadline of June 30, 2022.
NOTE: The term “non-facilities-based small voice service provider” means a small voice service provider offering voice service to end-users solely using connections that are not sold by the provider or its affiliates. (Federal Communications Commission, FCC 21-122)
Bicom Systems’ In-house STIR/SHAKEN Solution
Coming Soon – PBXware STIR/SHAKEN Implementation
We are happy to announce that this June, Bicom Systems will officially launch a full STIR/SHAKEN implementation for PBXware. We have decided to develop our very own Caller ID authentication framework for two simple reasons:
1) Our clients do not have to pay for expensive subscriptions for STIR/SHAKEN extensions for their business.
2) Our client’s data does not have to route through third-party service provider networks.
However, it’s crucial to note that every one of our partners must still get an SS certificate.
How Does It Work?
In a nutshell, PBXware will be able to handle both incoming and outgoing call verification.
For incoming calls, a public key, or more accurately, the URL to that key (which is hosted by one of the STIR/SHAKEN vendors), is included in the SIP header (of the incoming call). The call is approved once the key is downloaded and reviewed that is signed by an authorized vendor.
So, PBXware reviews encrypted SS information and allows the call if everything is in order.
When it comes to outgoing calls, PBXware signs every call based on the certificate that each user must obtain and implement in their PBXware.
Steps Required to Become STIR/SHAKEN Compliant
There are a few mandatory steps to be completed before becoming eligible for the Complete STIR/SHAKEN implementation. Keep in mind that the procedure can take several weeks, even months.
Step 1: Register with the FCC
For a new voice service provider, the first step is to register with the FCC by obtaining an FCC Registration Number – a 10-digit number assigned to a business or individual registering with the FCC. After that, you need to submit the filing to the Robocall Mitigation Database.
For the official Robocall Mitigation Database External Filing Instructions provided by the FCC, click here.
Step 2: Register with USAC (499 ID)
After registering with the FCC and obtaining your FRN, the next step is registering for a 499 ID at USAC. You can find a guide on registering for a 499 ID on their website.
This procedure usually takes 2-4 days to complete.
Step 3: Acquire your OCN
An OCN acronym stands for Operating Company Number, a four-character code assigned by the National Exchange Carrier Association (NECA), and it’s one of the requirements for the STI-PA Authorized Service Provider application.
To find out more about OCN and how to apply for it, head over to the NECA’s website. This procedure can take up to two weeks to complete.
Step 4: Submit your application to STI-PA
The only method to make or receive verified calls within the SHAKEN framework is to become an authorized provider, which is a strictly restricted procedure.
The conclusion of this procedure will depend on several factors, but it usually takes from one to three weeks.
Step 5: Confirm your Complete Implementation of STIR/SHAKEN with RMD
To confirm your network’s implementation of STIR/SHAKEN, head over to the Robocall Mitigation Database and update your filing.
- Providers who are subject to a shortened extension are:
- Non-Facilities-Based Small Voice Providers
- Small Voice Service Providers Found to Be the Source of Illegal Robocalls
- Bicom Systems’ complete STIR/SHAKEN solution is coming soon to PBXware.
- Every Bicom Systems client must apply for the STIR/SHAKEN certification. After finishing the registration process with the STI-PA and obtaining the Public token, the next step is implementing the SHAKEN extension within their PBXware.
- PBXware will sign outgoing calls and verify incoming calls before permitting them.
We encourage you to contact our Sales department so we can shape the best possible solution for your UCaaS business. Also, do not forget to visit our website and learn more about PBXware and our other products.
Disclaimer: All material in this publication is provided for educational purposes only and does not represent legal or regulatory advice. Bicom Systems strongly advises all voice service providers to obtain legal and/or telecom compliance advice on their company’s STIR/SHAKEN and other FCC rules and regulations requirements.
All content in this blog post is based on FCC-21-122A1, issued on December 10, 2021, and is subject to change if/when the FCC releases more information.