Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:43 pm
The origin-ID's purpose is to provide traceback to the origin of the call, expected to be used by law enforcement.
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics» Based on the callflow diagrams, all SIP carriers between Originating carrier and Terminating carrier must support TCP SIP and allow the extended headers to be forwarded, correct?
» So the origination ID would be the SHAKEN service point and carrier that first authenticates the 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)?
» 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 to figure out the number of concurrent call now
» So the origination ID would be the SHAKEN service point and carrier that first authenticates the 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)?
» 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 to figure out the number of concurrent call now
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