mercredi 1 avril 2020

FCC orders all carriers to implement anti-robocall technology by June 2021

A few major carriers have already started using STIR/SHAKEN to authenticate calls.

What you need to know

  • The U.S. FCC has instructed all carriers and phone companies to implement the STIR/SHAKEN protocol by June next year to combat the robocall menace.
  • STIR/SHAKEN will help lessen the effectiveness of illegal spoofing and enable carriers to identify illegally spoofed caller ID info even before the calls reach subscribers.
  • American consumers reportedly lose $10 billion annually to fraudulent robocall schemes.

The Federal Communications Commission (FCC) today adopted new rules that require the industry-wide implementation of the STIR/SHAKEN protocol to combat spoofed robocalls. All carriers and phone companies in the U.S. must enable called ID authentication on their networks using STIR/SHAKEN by June 30, 2021.

The new regulatory requirement is aimed at significantly lowering the effectiveness of illegal spoofing, allowing law enforcement agencies to identify scammers more efficiently, and helping carriers identify spoofed robocalls before those calls reach subscribers.

As per the FCC, eliminating the wasted time caused by illegal robocalls could save more than $3 billion annually. It also says that American consumers lose approximately $10 billion annually to fraudulent robocall schemes.

Even though the FCC had asked carriers to adopt the STIR/SHAKEN protocol in 2018, only a few carriers have rolled out the technology so far. Moreover, authentication is available only on select phones and the systems currently in place aren't integrated to work across networks.

The Congress had passed the TRACED Act in December last year, which mandated the protocol to identify illegal robocalls and gave the government new powers to find and prosecute robocallers.

How to enable Caller ID and spam protection on the Galaxy S20



from Android Central - Android Forums, News, Reviews, Help and Android Wallpapers https://ift.tt/2JvW1Za
via IFTTT

Aucun commentaire:

Enregistrer un commentaire