latency added to call setup while Shaken verification and certificate verification with a CA will be a concern for service providers
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
latency added to call setup while Shaken verification and certificate verification with a CA will be a concern for service providers
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:46 pm
It's been our experience with ClearIP that the total delay in call setup is less than 50ms. Also, as the media does not pass through this process, there is no additional latency added to the voice path.
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics» for calling Service providers, that is big in the health care space where service providers make calls on behalf of healthcare providers
» So the origination ID would be the SHAKEN service point and carrier that first authenticates the call?
» Should we have a certificate per DDI? or a certificate per service provider?
» 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?
» So SBC need to integrate with SHAKEN or is there any possibility where both service can be in single box?
» So the origination ID would be the SHAKEN service point and carrier that first authenticates the call?
» Should we have a certificate per DDI? or a certificate per service provider?
» 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?
» So SBC need to integrate with SHAKEN or is there any possibility where both service can be in single box?
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