Skip to main content

New technology could prevent neighbor-spoofed robocalls if implemented

As an update to my previous post, there is apparently some movement afoot to implement a method of secure verification of caller ID info.  It is similar to how e-mail and websites are encrypted and authenticated, using certificates.

STIR/SHAKEN is a technology standard that incorporates an authentication service, a verification service, and a certificate repository.  When a call is made, the authentication certificate issued by the caller's provider is looked up by the recipient's provider, and the call info is verified as being authentic or not.

The standard appears to be designed to be implemented at the service provider level.   As I stated previously, carriers will be slow to adopt anything that will cost them money, due to the amount of power they wield, and this case is no exception.  The call for them to adopt such a standard was put out by the FCC in 2014.  Nonetheless, 5 years later some providers, including Verizon, are going public with announcements that they intend to implement this standard, which would conceivably have a major impact on the type of robocalling - and by extension, the entire robocall industry.  By preventing the misuse/abuse of caller ID information, customers can then, in turn, effectively utilize tools such as spam filters to recognize and block calls from spammy sources.

As for when this all happens, Verizon says that in March, 2019 they begin offering their anti-spam service for free for their wire-line customers, which they say supports the STIR/SHAKEN call authentication.  Even if you are not a Verizon customer, it is a good thing for it to be adopted by any of the big providers.  At worst, it will reduce the cost effectiveness of these robocalls, and the volume will begin to drop, which will affect everyone.

Let's all hope this happens without a hitch, and our telephone infrastructure can become sane again.

Comments

Popular posts from this blog

Timbaland rips off a Demoscene artist

I knew this day would come. The new Timbaland/Nelly Furtado song "Do It" uses a song made in 2000 by Finnish demoscene artist "Tempest" (Janne Suni). It's a 4 channel .mod (the ripoff is from a playback using the C64 SID soundchip). The song was hosted on scene.org's servers (the main repository for all everyones demos and tracked music, etc.). As you might expect, no permission or royalties were paid to Tempest. Just to clarify, we're not talking about some kind of coincidence here. There is no question that this track was used to create the song "Do It". In an interview, Timbaland tries to downplay it, saying things like "he sampled it from a video game". (This track was not written for a video game- it was actually written for the 2000 demoscene music competition, in which it won 1st place). Regardless, he basically claims he has no legal obligations because it's just like all the other pop artists that sample other m

Reaper, Linux, and the Behringer X-Air - Complete Studio Solution, Part 1

Introduction and Rationale This is part one of a major effort to document my experiences with recreating my home studio, entirely using Linux.  Without getting into too many of the specifics, a few months ago I decided that I was unhappy with Windows' shenanigans - to the point that I was ready to make a serious attempt to leave it behind.  For most in this situation, the obvious choice is to switch to Mac OS.  With its proven track record, support, and options for multimedia production, it is naturally the first alternative to consider if your goal is to simply use something other than Windows. For me the choice was not so simple. I despise Mac OS and, in general, the goals and philosophies put forth by Apple in an effort to ostensibly provide users with an "easy" working environment.  It does not help that I have also failed to find any aspect of the Mac OS UI intuitive, but I realize that this is a subjective matter. With my IT background and user-control* favori

Windows 8 audio clicks and glitches narrowed down to Malwarebytes

Ever since I got my Windows 8 PC, I have been having serious problems with audio.  Basically all sound playback on my system experiences a brief  but frequent click, skip, glitch, stutter, whatever you prefer.  I can reproduce the issue on any sound card or firewire sound interface (devices tested include the onboard Conexant SmartAudio HD, my external Phonic Helix 12, and my Edirol FA-101).  All of them seem to have audio clicks, with the firewire interfaces' clicks seeming more harsh for whatever reason.