Share on LinkedInShare on LinkedIn

ARTICLE · 20 JULY 2021

TCPA Regulatory Update — STIR/SHAKEN And Robocall Mitigation Database Implementation Take Effect

Mintz, Levin, Cohn, Ferris, Glovsky and Popeo, P.C.
Mintz, Levin, Cohn, Ferris, Glovsky and Popeo, P.C.
Contributor
Mintz, Levin, Cohn, Ferris, Glovsky and Popeo, P.C.

Mintz, Levin, Cohn, Ferris, Glovsky and Popeo, P.C.

Mintz is a litigation powerhouse and business accelerator serving leaders in life sciences, private...

View firm profile
Explore more from Mintz, Levin, Cohn, Ferris, Glovsky and Popeo, P.C.

America's largest voice service providers are now using STIR/SHAKEN caller ID authentication standards on their Internet Protocol ("IP") networks.

United StatesMedia, Telecoms, IT, Entertainment

America's largest voice service providers are now using STIR/SHAKEN caller ID authentication standards on their Internet Protocol ("IP") networks. Pursuant to the FCC's March 2020 Report and Order (summarized here), as of July 1, all voice service providers and intermediate service providers not subject to an extension were required to implement the STIR/SHAKEN call authentication framework within their IP networks. Those providers whose networks were previously non-IP based were required to either upgrade to implement STIR/SHAKEN or develop some other non-IP based robocall mitigation program. Voice service providers and intermediate providers had to certify that they were STIR/SHAKEN compliant or had a robocall mitigation plan in place, through FCC's Robocall Mitigation Database, also no later than June 30. Those that failed to certify may face FCC enforcement action including a possible monetary forfeiture.

We operate a free-to-view policy, asking only that you register in order to read all of our content. Please login or register to view the rest of this article.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

See more popular content from