November 7th, 2018 | 11am EST

The C15 continues to evolve with Release 15 offering new functionality, meeting regulatory requirements, and delivering customer’s requests.

Watch on-demand as we discuss all the below and more.

Topics Covered on the webinar include:

  • Regulatory changes
  • Cordell Analytics powered by C15 Call History Server
  • Numerous customer requests
  • An early peek at Release 16
  • Q&A
Elizabeth Page | Ribbon Communications
Elizabeth Page
Director, IOC Sales
Ribbon Communications
Lee King | Ribbon Communications
Lee King
Director, C15 and DMS10 Design and Support
Ribbon Communications

WEBINAR: Ribbon C15 Release 15/h2>

November 7th, 2018 | 11am EST

 

C15 Release Update

So what's happening in the IOC market? There's a number of regulatory things that are coming on that are that are interesting and we're addressing them in various ways. I want to go over a few of those. One of them is within the last year or so the FCC has come out with this 17-132A ruling which says that carriers are allowed to or are obligated to provide law enforcement with information relating to threatening calls. In particular the calling number. So if it's available, the C15 can provide that. The way we can do it is two-fold, one is with the call history server. You can actually go into Wireshark and pull up the calls that were delivered to whatever number is in question and then we can go in if the number was delivered to us to find the number of the calling party and provide that to law enforcement. Another way you can do it, a much better way, is with an analytics program that we've added that provides a really nice easy way to find information like that. There are two different ways to get it both of them require our call history server because that's where we store the details of all the calls that are coming in.

Another thing that's come out in this last year is the expanded number of toll-free HNPas and on the c15 we had a limit of eight, but we've increased it to 17. I believe this year the eighth one will be assigned so going forward we will now support up to the maximum number that can be assigned which is17. One of the new ones that have come out is 833 and that's coincidentally going to be the new number that you can call for support. You can call 833-Ribbon1 for support. We still use the Express routing code 1044 for the C15, the existing 866-GENBAND number still works, but we will be transitioning to the Ribbon1 number. That does work now and you could use it if you want too.

Another hot topic these days is STIR/SHAKEN, in fact, Chairman Pai came out with a letter yesterday (I actually heard a discussion of this on NPR on my way to work in the morning) but Chairman Pai came out with a request about stopping robocalls. It's specifically talking about STIR/SHAKEN which is the protocol to address that. This has been out there for a couple of years and there's been a number of questions about it. Some of the things to consider are this is a network-wide issue and it's not just an endpoint issue. In particular, it's the long-distance carriers that are delivering those calls to the endpoints. There are multiple components of the way this will be addressed. The Ribbon SWe SBC already supports STIR/SHAKEN with their 7.2 release. They don't make routing decisions but they do handle the protocol at this point. The PSX which is our routing and policy switch is planning, in Q2 of next year, to have the ability to make routing decisions based on the attestation of the call. The attestation of the call means that it is known to be a non-spoofed number, it got a certificate when it was originated and that certificate carried through until it's terminated. So you know that the call is a valid call. This only applies if you've got an end-to-end SIP network. As soon as you leave the SIP network and go into the TDM world then that information is no longer passed through. The applicability for the endpoints we're still evaluating, so the C20 in the C15 we're both looking at this together and deciding exactly how we need to implement STIR/SHAKEN within our two switches. The point of this is really to eliminate robocalls and eliminate nuisance calls.