[VoiceOps] STIR for intra-net calls

[Calvin Ellison]

It's important to note that if there is any call forwarding involved, you'd
want to start off with a properly signed call to support the additional div
passport(s).



Calvin Ellison

Systems Architect

calvin.ellison at voxox.com

+1 (213) 285-0555

<http://voxox.com>

<https://www.facebook.com/VOXOX/> <https://www.instagram.com/voxoxofficial/>
<https://www.linkedin.com/company/3573541/admin/>
<https://twitter.com/Voxox>

The information contained herein is confidential and privileged information
or work product intended only for the individual or entity to whom it is
addressed. Any unauthorized use, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify me immediately.


On Mon, Jun 27, 2022 at 3:01 PM Nathan Anderson <nathana at fsr.com> wrote:

> Alex Balashov wrote:
>
> > Or are we talking about customers who do get the full attestation
> headers and interrogate them?
>
> Precisely this.  If we ever get such a customer, and if at that time we've
> finally arrived at a world where it's expected that 100% of inbound calls
> [at least at provider's edge] are attested, and thus this customer's
> expectations have been calibrated to expect the same of calls that they
> receive via us (and they're planning on dropping any inbound calls without
> a valid PASSporT) even though they are paying us for SIP trunking and
> aren't a "peer" of ours, if a different customer of ours calls them, are we
> supposed to generate & transmit an Identity header for that INVITE?  It
> seems weird to do so, but I could potentially see such a scenario playing
> out, eventually.
>
> -- Nathan
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20220627/586283bf/attachment-0001.htm>