Hi Greg. In our use case, we purchase DIDs from them. So, they are the
inbound carrier (they are a CLEC and IPES) and STIR/SHAKEN Service
Provider. However, we do not use them for termination. They offer service
termination, but we do not use them due to existing contracts. So, in
order to have our calls signed, we needed them to do it. The biggest issue
we've come across is the number of companies *able to *provide this service
is limited, especially to the Asterisk community. I stress able to because
even though some companies are Service Providers, they are simply not
technically capable of offering it.
I will send you my contact's information at TILTX privately. He's a
subject-matter expert with the STIR/SHAKEN framework and he's offered us
invaluable help.
Thanks,
Alex
On Sun, Mar 7, 2021 at 1:43 PM Greg Troxel <gdt at lexort.com> wrote:
>
> Alexander Perkins <alexanderhenryperkins at gmail.com> writes:
>
> > They ended up creating an AGI script for us that handles everything.
At
> > the end of the day, all we needed to do was pull down the script, and
add
> > the exten => s,n,AGI(TILTX-SHAKEN.agi) command and it handles
> > everything else.
>
> I wonder if you could step back and explain the big picture, as I'm not
> really following this. As I understand it:
>
> usually asterisk is used as a pbx
>
> STIR/SHAKEN is a protocol run between carriers to prove the authority
> to use the claimed callerid
>
> when someone gets service from a carrier and connects to it from
> asterisk, I would expect the carrier to basically filter the claimed
> callerid to be from the set of values recorded with your account as
> legit, and for the carrier to do the STIR/SHAKEN authentication.
>
> So I wonder if your asterisk instance is connecting to the PSTN as a
> top-level carrier, or, more likely, I am confused in some way.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20210307/5136b3e7/attachment.html>