FCC Revises STIR/SHAKEN Service Provider Requirements

By Maurice Nagle December 01, 2020

The United States Federal Communications Commission – better known as the FCC (News - Alert) – has a lot on its plate, to say the least. When the nuisance that is robocalls earned public enemy status, STIR/SHAKEN was put in place, but initial policy implementation didn’t quite cover all the bases.




Today, the FCC announced that based on recommendations from the Cloud Communications Alliance (CCA) the Secure Telephone Identity Governance Authority (STI-GA) will abridge requirements in robocall prevention policy.

“Under the previous policy, many VoIP providers – including CCA members – were disqualified from participating in the call authentication framework even though the FCC would require participation," said Mark Iannuzzi, Chairman of CCA Government Affairs Committee and CEO of TelNet (News - Alert).

Specifically speaking, the new FCC policy allows CCA members to leverage STIR/SHAKEN via FCC Robocall Mitigation Database. The initial policy put forth by STI-GA required service providers have direct access to telephone numbers, disqualifying a number of CCA members from implementing STIR/SHAKEN and creating an environment for competitive disadvantage.

"This is great news not just for providers, but for their customers and consumers who will be better assured of the identity of callers. In turn, providers will be able to more quickly and accurately trace back to the source of a call and identify bad actors easily,” Iannuzzi continued.

How are robocalls impacting your business?




Edited by Maurice Nagle
Get stories like this delivered straight to your inbox. [Free eNews Subscription]
SHARE THIS ARTICLE

From Visibility to Action: Pure IP Is Rethinking Enterprise Technology Cost Management

As distributed enterprises struggle with rising carrier costs, unused services, billing errors and complex infrastructure, continuous technology cost management is emerging as a more effective way to control spend and uncover savings.

Read More

90% of AI Voice Projects Fail, But Not Because of the AI

Enterprise Agentic Voice projects succeed or fail not on AI capability alone, but on the integrations, governance, workflows, data access, and operational architecture required to move AI voice agents from impressive demos to reliable production systems.

Read More

Snom and Telinta Make Automated Provisioning a Competitive Advantage

Automated provisioning and integrated device lifecycle management are helping UCaaS and hosted voice providers reduce deployment costs, improve scalability, support resellers more efficiently, and strengthen customer experience.

Read More

Your AI Agent Isn't a Phone System

Enterprise AI voice agents do not replace business phone systems-they depend on communications infrastructure to route calls, transfer conversations, enforce policies, integrate workflows, and orchestrate interactions between AI, employees, customers, and business applications.

Read More

Telcos Have Working AI Agents, Becoming AI-Native Is the Harder Part

Operators are moving agentic AI into production, but they have to address the harder challenges of legacy systems, data architecture, governance, workforce change, and turning network intelligence into new revenue.

Read More