will this be implemented for foreign originated calls initially?
Telcobridges - Session Border Controllers :: General :: FAQ :: Battling Robocallers with STIR/SHAKEN
Page 1 of 1
will this be implemented for foreign originated calls initially?
by alan.percy@telcobridges.c Thu Feb 21, 2019 3:51 pm
Foreign originated calls should have attestation of "C" (or none).
alan.percy@telcobridges.c- Number of Messages : 60
Point : 176
Registration Date : 2019-01-14
Similar topics» 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?
» Inbound calls are working but outbound calls are failing for SIP Trunk
» How do you trap calls on SIP trunks - TDM is easy to do and provide from the carrier - What about SIP threats - like bomb threats, harrassing calls
» Are Service Provider still having issues with Codec Mismatch? i.e. Company A is using G.711 calls Company B using G.729 - Company B only accept G.729 calls only, are Service Provider have capability to match the codecs?
» how will this implement calling card calls and other calls that have a dial in number?
» Inbound calls are working but outbound calls are failing for SIP Trunk
» How do you trap calls on SIP trunks - TDM is easy to do and provide from the carrier - What about SIP threats - like bomb threats, harrassing calls
» Are Service Provider still having issues with Codec Mismatch? i.e. Company A is using G.711 calls Company B using G.729 - Company B only accept G.729 calls only, are Service Provider have capability to match the codecs?
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