@JaredBusch said in What is Skyetel going to do about SHAKEN STIR:
First, @Skyetel has a lot of identity verification built into the sign up process. So the odds of having people abuse their system is low.
But, currently, I can send out what ever CID I want on my Skyetel trunk. This is good for me right now as I am migrating a site and I want to route my outbound calls before the numbers port in.
But I have a feeling this will not pass muster with WTF ever the FCC or Congress eventual spew out. Current the proposal is call SHAKEN/STIR (https://www.fcc.gov/call-authentication).
Mostly I am just curious. Nothing impacts me at the moment, but it most certainly could impact me, so it is always good to keep things like this in mind.
I can go on the longest rant about the futility of STIR/SHAKEN, but I'll avoid that here. The bottom line is its going to take years to implement, and at best, only validate that the person calling you is indeed who they are saying they are. Blocking unwanted calls is completely and totally different from validating CID information (which is, on the whole, mostly accurate). I much prefer Apples approach: https://www.macworld.com/article/3405536/how-to-use-ios-13s-new-silence-unknown-callers-feature-to-fight-phone-spam.html
My hope is that Apple/Google beat Congress to the punch and roll out a solution that just closes the door on this problem - they actually have the data that matters. That is - who the end user actually wants to accept calls from.
To answer your question though - we have to wait till our PSTN interconnects implement it on their network before we can do it on ours. It requires a sort of chain of authenticity, and us sending a compliant call to a network that can't interpret it will result in failures. This will take some time - our outbound gateways use around 12 different networks, and each of those 12 have about 10 of their own. I would not be surprised if this takes 5 years - and I have no idea how it will work with Canadian carriers that are 10 years behind the technology of US carriers.
There is a great deal of confusion around how to verify the caller ID - but my best guess is something like a test call will be placed to the number you provide, and if you approve it via some kind of pin, you'll be able to use that outbound CID with an associated approved CNAM. A lot will depend on the carrier delivering the call to the subscriber (Verizon Wireless, T-Mobile, etc) and what standards they want. (This is part why I don't like this - it gives way too much power to the last mile).
We obviously plan on being compliant and implementing this as soon as a standard is settled - We hate spam calls as much as you do (hence our spam blocking feature). We'll announce much more details when we have them - but we're probably a year away at least.
