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
So the origination ID would be the SHAKEN service point and carrier that first authenticates the call?
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:48 pm
That is correct - the first SIP service provider to handle the call will apply the identity token and assign the origin-id.
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics» latency added to call setup while Shaken verification and certificate verification with a CA will be a concern for service providers
» Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
» 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?
» How do service providers take action on bad calls that have entered the sip network at some point and are signed?
» So SBC need to integrate with SHAKEN or is there any possibility where both service can be in single box?
» Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
» 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?
» How do service providers take action on bad calls that have entered the sip network at some point and are signed?
» 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