Ani, How is GCS supporting this whole STIR/SHAKEN, SHAKEN/STIR, or SHAKEN NOT STIRRED thing? Which James Bond fan came up with this stuff anyway?
LOL. Good question my friend. Yeah, sometimes the engineering geeks in the world of telecom like to think they are clever, and obviously these folks must have been James Bond fans. Me, personally, I am a traditionalist. Sean Connery is, and will always be, the best Bond. But Daniel Craig has been crushing it lately! Anyway, sorry, off track there. Back to the Stir Shaken protocol.
According to the FCC, the SHAKEN/STIR (that’s the actual naming convention) is an acronym for: Signature-based Handling of Asserted information using toKENs (that’s the SHAKEN part) and the Secure Telephone Identity Revisited (STIR). Basically, this is the new protocol that is being pushed in response to the public demand to combat illegal caller ID spoofing which is part and parcel of robocalls.
According to the FCC, “Once implemented by carriers it should greatly help the accuracy of caller ID information and should provide consumers with helpful information for determining which calls are authenticated.” It is a framework that uses tokens passed between originating and terminating carriers that authenticates that the originating call came from the actual subscriber assigned to that number. In other words, it puts the whole caller ID spoofing trick to bed.
How is GCS responding to it? We’ve updated our GCS Interconnect Command Platform to support the passing of the SHAKEN/STIR protocol. The GCS ICP has the ability to transport SIP via TCP rather than traditional UDP. We are also working on having the ability to verity and authenticate SHAKEN/STIR tokens and apply specific treatments based on results. It’s just another example of how GCS responds to the ever changing landscape of voice communications.
Now, all this talk about SHAKEN/STIR has made me nostalgic for a classic James Bond movie and a martini!