1. Enterprise Structure For Use Case Application of Various Token/Cert Proposals
Presented by: Rebekah Johnson

2. The Enterprise Who is calling? I can be trusted.
You wanted me to call you.
Who is calling?
Can I trust the identity?

3. The Enterprise
Multiple
Terminating Carriers

4. Platform Multiple Multiple Originating Carriers Terminating Carriers …
Call Center
Multiple
Originating Carriers
Multiple
Terminating Carriers

5. Platform Multiple Multiple Originating Carriers Terminating Carriers …
Call Center
Multiple
Originating Carriers
Multiple
Terminating Carriers …
Call Center
Platform

6. STIR/SHAKEN Framework
Platform …
Call Center
Multiple
Originating Carriers
Multiple
Terminating Carriers
STIR/SHAKEN Framework
“Authorized to use TN” …
Call Center
Platform

7. STI-PA
STI-CA
TN Provider
Reseller SP
OSP

8. STI-PA
STI-CA
Call Center/BPO
TN Provider
Reseller SP
OSP
Cloud Solution
Bad Actor

9. STI-PA
STI-CA
Call Center/BPO
Enterprise
TN Provider
Reseller SP
OSP
Cloud Solution
Enterprise
Enterprise
Bad Actor
MULTIPLE
Terminating SP

10. STI-PA
STI-CA
STI-CA
Call Center/BPO
Enterprise
TN Provider
Reseller SP
OSP
TN SP
OSP
Cloud Solution
Enterprise
Call Center /BPO
What is end goal?
What does delegate cert, LEMoN Twist, STIR or any other proposal achieve or improve?
Who benefits -Enterprise, Consumer, Originating Carrier, Enforcement, Analytics?
Enterprise
Bad Actor
Enterprise
MULTIPLE
Terminating SP

11. Enterprise Impact and Considerations
Minimal to no impact on outbound configurations/strategies to maintain use of voice channel
Expectation of outbound solution partner to ensure calls trusted
Struggles to understand how analytics and STIR/SHAKEN impact calls “because they have consent”
Insight into how STIR/SHAKEN impacts their calls. What is the relationship they should have with solution provider and/or TN provider?
Should I be requiring my solution provider to “sign my calls”? What does this mean?
I AM trusted.
You wanted me to call you.
I know who is calling.
I trust the identity.