Top ten blog posts in 2020
Here are the top ten blog posts, based upon readership, that we ran in 2020.
- Update caller display name to advise customers of potential spam calls. Call authentication and analytics can identify potential spam calls. There isn’t yet a standard for display relevant information to the called party, but standards are emerging. Here’s an overview.
- Comments on caller ID authentication best practices. The CATA Working Group of the NANC issued a best practices document, and the FCC asked for comments. Here’s a summary of the feedback they received.
- International SHAKEN — how that might work. Initially, STIR/SHAKEN will be rolled out country-by-country. Ever wonder how these separate deployments might be joined together? Here’s a quick overview of a roadmap for that.
- Should US service providers file for the voluntary SHAKEN exemption? The TRACED Act directed the FCC to allow voice service providers to file for a Voluntary STIR/SHAKEN Implementation Exemption in 2020. Should you do that? We cannot and would not offer legal advice, but we can share some information that might be useful as you ponder this situation.
- FCC issues STIR/SHAKEN mandate. On March 31, 2020, the FCC issued a mandate for telephone companies to implement STIR/SHAKEN call authentication to combat spoofed robocalls. Here are the highlights.
- Who may authenticate calls for STIR/SHAKEN. STIR/SHAKEN provides a way to authenticate caller ID as a safeguard against spoofing, a common robocall tactic. The framework relies on a governance structure that vets and approves who can authenticate calls. This blog post gives an overview of the current policy around authentication approval in the U. S.
- FCC issues further rules on SHAKEN and robocall blocking. The FCC today published the next round of rules for robocalls and STIR/SHAKEN deployment. There’s quite a lot in this 93-page document. We’ve summarized it for you here.
- Robocall mitigation program mandate. The FCC‘s Second Report and Order on SHAKEN deployment extended deadlines to deploy STIR/SHAKEN in some situations. However, any provider that accepts one of these extensions must deploy a robocall mitigation program by June 30, 2021. Enforcement is strict. Here‘s what that means.
- STIR/SHAKEN mandate signed into U. S. law. The Pallone-Thune TRACED Act was signed into law on December 30, 2019. This legislation includes several measures to combat unwanted robocalls, including a mandate for voice service providers to use STIR/SHAKEN call authentication.
- TRACED Act calls for one-ring scam protection. The Pallone-Thune TRACED Act includes requirements for the FCC to initiate a proceeding to protect called parties from one-ring scams (also known as Wangiri, Japanese for one-and-cut). Here’s an overview of one-ring scams, the roadmap for this FCC directive, and what protection looks like.
We offer STIR/SHAKEN and robocall prevention solutions in our ClearIP and NexOSS software platforms.
In addition, we help service providers with all aspects of STIR/SHAKEN deployment, including registering with the Policy Administrator and filing their certification with the FCC.
Contact us today to learn more.
This information will only be used to respond to your inquiry. TransNexus will not share your data with any third parties. We will retain your information for as long as needed to retain a record of your inquiry. For more information about how we use personal data, please see our privacy statement.
STIR/SHAKEN information hub
Whitepapers, videos, and more