By Alan Percy, Senior Director of Product Marketing, TelcoBridges
The battle to tame fraudulent robocalling made some significant advancements this week as the SIP Forum released two new technical reports.
If you’ve been following along, you know that fraudulent robocalling and caller-ID spoofing have become the tools-of-the-trade for criminals trying to trick unsuspecting victims into their scams. (By now you’ve come to realize that you can’t trust the caller-ID on your phone.) The FCC and the CRTC have put deadlines in front of the carriers, requiring implementation of secure caller-ID technologies to prevent spoofing of caller-ID.
The first specification Technical Report on a Framework for Display of Verified Caller ID (ATIS-1000081) defines a standard user experience for calls from known callers, likely SPAM callers, suspect and potential fraudulent callers with color icons and information on screen-based devices. The specification details the user experience study that went into the graphical images, providing data on real-world user responses and behaviors to the information displayed.
The second specification Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server provides a proposed RESTful API for the implementation of the SHAKEN specification, used to authenticate and verify caller-ID for network-based calls. This recommendation is an alternative to the SIP-based mechanism as specified in the SHAKEN recommendations, as is currently used by a number of vendors, including TransNexus and TelcoBridges.
“These two new resources are critical to helping service providers implement SHAKEN,” said ATIS President and CEO Susan Miller. “They are products of ATIS’ continued collaboration with the SIP Forum and are instrumental to industry efforts to address the robocalling problem and maintain consumer trust in the voice network.”
“The SIP Forum is committed to working together with ATIS to continue to develop the operational documents for the SHAKEN Framework, and these two new reports provide important additional guidelines and details essential to the successful deployment of the SHAKEN standard,” said SIP Forum Chairman Richard Shockey.
In addition to the above announcement, we’ve made significant progress with TransNexus on their SHAKEN fraud prevention framework, recently posted detailed configuration notes on how to configure both FreeSBC and TransNexus OSPrey server and completed our bench testing milestones.
Looking ahead and demonstrating the level of interest on the topic, a dedicated track and session on Robocalling is scheduled for SIPNOC 2018.