Since this requires token generation on origination and verification on the terminating carrier, do we have stats on how much PDD we expect to be added to a callflow?
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
Since this requires token generation on origination and verification on the terminating carrier, do we have stats on how much PDD we expect to be added to a callflow?
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:44 pm
For this demo call, 41 ms of PDD was added to add SHAKEN functionality. This is typical for a stup of this nature.
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics» Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
» latency added to call setup while Shaken verification and certificate verification with a CA will be a concern for service providers
» Do we have any real world examples of the transaction costs for the token generation per call?
» How granular do you expect the origid assignments to be (e.g., at the originating interface, at the sbc, at the carrier, or some other level)?
» So the origination ID would be the SHAKEN service point and carrier that first authenticates the call?
» latency added to call setup while Shaken verification and certificate verification with a CA will be a concern for service providers
» Do we have any real world examples of the transaction costs for the token generation per call?
» How granular do you expect the origid assignments to be (e.g., at the originating interface, at the sbc, at the carrier, or some other level)?
» So the origination ID would be the SHAKEN service point and carrier that first authenticates the call?
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