STIR/SHAKEN IMPLEMENTATION FOR US/CANADINAN MARKET

[syedfahim786]

Hello All,

We ran into some issues recently. Where the call connectivity dropped significantly. It is just in the US market. We haven't worked in the US market since 2019. Things might have changed over the course of time which might have caused this. However, all of our carriers have implemented the STIR/SHAKEN on their network to give the attestation required to each call. As well we purchased DIDs from them directly to confirm the A attestation. We are currently making calls to TX, US.

We tried with multiple carriers, but all of them behaved the same. Do we need to make any changes within the Vicidial/Dialplan/Extension? Any suggestions will be highly appreciated.


Installation Details: Vicidial 9 | Scratch installed on Centos7 | Asterisk 13.29.2 | SVN Version 3558 | Version: 2.14b0.5 |

[mflorell]

The US market has changed significantly in just the last year. STIR/SHAKEN has allowed carriers to reject/re-route traffic arbitrarily as they see fit. We have had several client find success with using auto-rotating CIDs on a very short 5-minute rotation schedule over the course of 3 days, but this requires hundreds of CIDs to work properly.

[frequency]

The US market has changed significantly in just the last year. STIR/SHAKEN has allowed carriers to reject/re-route traffic arbitrarily as they see fit. We have had several client find success with using auto-rotating CIDs on a very short 5-minute rotation schedule over the course of 3 days, but this requires hundreds of CIDs to work properly.

Auto rotating after every 5 minutes in scenarios where people are dialing to wireless numbers more often can cause the big four to tag the caller id as "Scam Likely"/Spam Likely prematurely.

We do offer higher and bulk DIDs attested at A. You can revisit us in case you need help!