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)?
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
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)?
The origin-ID assignment is somewhat flexible, but the goal is to make it granular enough to correctly identify the source of any one call.
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?
» 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?
» Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
» Does FreeSBC hide the Media's Originating IP?
» Do you support multiple signaling and media realms? How 1+1 redundancy is handled on IP level, is it using floating IP address?
» 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?
» Does the origination ID mean that any downstream carrier can now figure out who the originating TSP entity was and seek their business directly?
» Does FreeSBC hide the Media's Originating IP?
» Do you support multiple signaling and media realms? How 1+1 redundancy is handled on IP level, is it using floating IP address?
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