STIR/SHAKEN plan of action
Sippy’s STIR/SHAKEN plan of action
Legislative mandates in the telecoms industry are nothing new. The STIR/SHAKEN rules passed by the US congress are neither unexpected nor ill-advised. Sippy strongly agrees that a healthy dose of good regulation might be a great way to both help our industry grow and to protect consumers.
In light of all the recent conditions and the upcoming STIR/SHAKEN rules, Sippy has begun preparations for releasing features and functionality aimed at ensuring that our softswitch provides the vital solutions you are going to need to remain compliant.
Sippy Software has already started testing our STIR/SHAKEN implementation during OpenSIPIT with some of the telecom industry’s great technical minds. This allowed for rigorous interoperability testing between different applications and platforms. The successful testing now allows us to move onto the next phase of our development plan.
We have recently partnered with 1 Call Connect to provide verified signatures. Our B2BUA sends an unsigned invite to 1 Call Connect’s systems and receives a signed 302 response. The signature is then added to the outgoing invite as part of the identity header as well as a date. With an API key from 1 Call Connect users will be able to use this service to sign the calls that are placed to meet with regulations in the US and Canada. This solution is currently being tested with real numbers and will be available in our Sippy 2020 release in the coming weeks.
If you choose to use the STIR/SHAKEN functionality we make available through 1 Call Connect, you will have to set up an account with them and cover the cost per token according to your agreement with them.
Finally we are currently working on an internal system for both Signing and Verification of STIR/SHAKEN. This will create a local DB containing the necessary tokens and signatures necessary for STIR/SHAKEN. Switch operators will be able to adjust their verification thresholds allowing for verification to be turned off, relaxed, or treated with Strict verification methods. This piece of work is still currently under development and more news will be coming in the following weeks.
We will be looking at having these changes available in our latest production version as soon as possible. Expect us to create some updated documentation for each of the described solutions up on our Support forum when these are released. We look forward to hearing your feedback to help us improve this feature and implementation.