STIR/SHAKEN – How to stop the robocalling madness

Tuesday, July 16th | 11am EDT

There were an estimated 5.2 billion robocalls in just March 2019. Join Ribbon & Neustar on July 16th to learn how to put a stop to robocalling!

Unwanted calls top the Federal Communications Commission’s (FCC) consumer complaint list. To protect consumers, the FCC and Congress are undertaking aggressive actions to combat unwanted, illegal robocalling and call spoofing; this includes implementing a requirement to adopt Caller ID authentication with the STIR/SHAKEN standard. The FCC is putting pressure on many service providers to have a solution in place by the end of 2019 - are you ready?!

While some service providers already have solutions in place and others are testing, a majority have not begun the process. Implementing STIR/SHAKEN needs expert advice; in this webinar on July 16th, you will learn more about the regulatory aspects, architecture, implementation challenges and deployment best practices for STIR/SHAKEN, with a focus on the following:

  • The impacts of unwanted robocalls and call scams on subscribers and enterprises
  • An update on the FCC’s June 2019 declaratory ruling to allow default call blocking
  • The business and technical aspects of deploying STIR/SHAKEN in your network
  • Recommendations to address the complexities of implementing STIR/SHAKEN
  • Incorporating network analytics to increase the efficiency and value of STIR/SHAKEN
  • Q&A
Ram Ramanathan | Ribbon Communications
Ram Ramanathan
Sr. Director, SBC & Policy
Ribbon Communications
Ricardo Bonassi | Ribbon Communications
Ken Politz
Sr. Product Management Director

WEBINAR: STIR/SHAKEN – How to stop the robocalling madness

Tuesday, July 16th | 11am EDT


STIR/SHAKEN – How to Stop the Robocalling

We're going to start off just with an update on the regulatory and legislative front, interesting times is an understatement I think in terms of anyone providing telecom service these days. From a regulator perspective, this topic really started taking traction last November when the FCC Chairman came out and the phone companies adopt authentication by the end of 2019. Both Rahm and I attended a Robocall Summit earlier this year, where Rahm also spoke, and he'll talk a little bit about that shortly. The FCC further came out with a green light defaulting robocall blocking. That was on June 6th and that introduces some interesting areas that we'll explore in more detail during this webinar. Interesting enough, this opens up the discussion of where we started with the legal robo-calling and spoofing and such has now kind of opened up into an all bets off to pretty much any type of robo-call, spoof-call or annoying call and giving some safe harbors and the abilities for carriers now to offer default Robo-call blocking on an opt-out basis. That introduces another requirement for carriers looking to support that ability. Lastly, on the legislative front is the fact that there are bills progressing where there's a joint Senate and House bill being drafted and some compromises across these. But I think that the bottom line here is that we're looking at a potential bill going in front of the President perhaps as early as September 2019 which will also include some mandates around some qualification and so forth around the robo-calls.

I'd like to take a couple of minutes to talk about the FCC summit that happened last week. Ribbon Communications and Neustar were part of the summit and the FCC invited Ribbon to be part of a panel. The purpose of the summit was for all the stakeholders to understand the status or the progress made in terms of stir shaken implementation by the different carriers, whether large, MSOs or smaller carriers and, what are some of the challenges that they're facing? A lot of the carriers have gone through either Neustars tests labs or have run interoperability tests among themselves and so what are some of the early challenges in terms of implementation that they've seen and what are some of the best practices that they've used to overcome these challenges? This is where the carriers of the vendors and the standards body come together and recommend best practices so that the carriers that follow don't face the same issues as the carriers that have already done some of the testing and implementation. This was kind of the purpose of the meeting of the summit.

The key takeaways from the FCC summit are as follows... From the first panel, which is for the large carriers, the key takeaways where the FCC has set a milestone for the end of the year for implementation of stir shaken which is basically signing and verification of calls. So, a lot of the carriers that participated in the panel are well on their way and tracking nicely towards the end of the year milestone for signing and verification. In terms of attestation levels even though there is an A, B, and C - A and B are the preferred ones based on the panel discussion and we'll talk about what A, B, and C mean as we go further in this presentation. For now, C is not preferred, obviously, there will be cases where C may need to be used maybe for internationally originated calls or international gateways. But in general A and B are preferred and A is obviously the most preferred that the industry would like to eventually see.

The panel also looked at some of the evolving standards so once we do the basic signing and verification there are other things that are being discussed in the standards. These include TN delegation where the carrier for example delegates the signing responsibility to to an enterprise or a non-carrier. There were discussions about enhanced caller ID or enhance CNAM this is how we can really tell an end-consumer whether it's a landline or a wireless end-consumer. We can notify them on the validity of the caller or really who's calling them so they can make an informed decision whether to pick up the call or not. Also, there were discussions about the policy administration framework. This contract has been awarded so the policy administration framework which basically uses the certificate management authority, and this will be available by the end of the year.

The key takeaways from the consumer-facing panel focused on two aspects. One is the caller ID display; the display needs to be simple give as much information as possible to the end consumer while making it very simple for them to understand. The other topic was about call blocking which the FCC ruled on June 6 that carriers can now block calls on behalf of customers. Customers will obvious have the capability to turn that off and accept all calls if they want to do that. But by default, that the preference will be to turn on call blocking for customers.