I assume you will cover full attestation, partial attestation, and gateway attestation?
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
I assume you will cover full attestation, partial attestation, and gateway attestation?
There is a great article here: https://transnexus.com/whitepapers/understanding-stir-shaken/
Full Attestation (A) — The service provider has authenticated the calling party and they are authorized to use the calling number. An example of this case is a subscriber registered with the originating telephone service provider’s softswitch.
Partial Attestation (B) — The service provider has authenticated the call origination, but cannot verify the call source is authorized to use the calling number. An example of this use case is a telephone number behind an enterprise PBX.
Gateway Attestation (C) — The service provider has authenticated from where it received the call, but cannot authenticate the call source. An example of this case would be a call received from an international gateway.
Full Attestation (A) — The service provider has authenticated the calling party and they are authorized to use the calling number. An example of this case is a subscriber registered with the originating telephone service provider’s softswitch.
Partial Attestation (B) — The service provider has authenticated the call origination, but cannot verify the call source is authorized to use the calling number. An example of this use case is a telephone number behind an enterprise PBX.
Gateway Attestation (C) — The service provider has authenticated from where it received the call, but cannot authenticate the call source. An example of this case would be a call received from an international gateway.
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics
» Is the attestation tied to a name of the entity behind the call or will CNAM dips still be needed?
» Convert demo to full license
» Doesn't this assume fraudulent calls are NOT being made off of established "legitimate" carrier networks. A valid certificate doesn't mean it's not a fraud call, does it? I may be missing something here.
» Is it fair to assume that most user-agent devices such as Polycom VVX phones, Yealink Phones currently do NOT support these new protocols? What about support from voice switches (broadworks). Do they know how to process the new headers appropriately?
» Script for Stir/Shaken with Neustar
» Convert demo to full license
» Doesn't this assume fraudulent calls are NOT being made off of established "legitimate" carrier networks. A valid certificate doesn't mean it's not a fraud call, does it? I may be missing something here.
» Is it fair to assume that most user-agent devices such as Polycom VVX phones, Yealink Phones currently do NOT support these new protocols? What about support from voice switches (broadworks). Do they know how to process the new headers appropriately?
» Script for Stir/Shaken with Neustar
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum