How do service providers take action on bad calls that have entered the sip network at some point and are signed?
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
How do service providers take action on bad calls that have entered the sip network at some point and are signed?
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:51 pm
As calls are signed at the point of entry, it is up to the originating service provider to "know their customer" and only attest to calls from known subscribers.
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
» How about calls originated outside NorthAmerica? (these countries won´t follow this STIR/SHAKEN protocol) Are these calls all be treated as "possible spoofed CLI" calls?
» how will this implement calling card calls and other calls that have a dial in number?
» 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
» How about calls originated outside NorthAmerica? (these countries won´t follow this STIR/SHAKEN protocol) Are these calls all be treated as "possible spoofed CLI" calls?
» how will this implement calling card calls and other calls that have a dial in number?
» 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
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