virtualmike wrote:george_byrd wrote:virtualmike wrote:Let's hope that SHAKEN/STIR rises up to the challenge.
As I said, my understanding is outdated by decades. What little I know of SHAKEN/STIR is that spam call blocking requires some degree of human sleuthing by carriers to determine which IP or IP block to refuse (or block) based on one or more spam calls.
I am generally satisfied that Sonic does a good job of it.
I am generally disappointed that the state and federal DOJs have taken no real initiative to locate and prosecute the perpetrators. Even foreign actors can still be indicted, prosecuted in absentia, and arrested if they set foot on US territory or on another nation with extradition treaties.
DOJ has successfully done that to other foreign perpetrators in the past. Historically, even a DNA sequence has been indicted. As has been observed before, any prosecutor can indict a ham sandwich if he really wants to.
The DOJ could also prosecute the robospammer stateside co-conspirators, down to the lowest level.
They could indict every co-conspirator with millions of counts of fraud, based on the numbers of robocalls made by their bosses.
But DOJ has done none of that. Instead, they throw up their hands and say "we can't do anything about it because it's too difficult to prosecute, so we'll lean on the private sector carriers to prevent it."
Since this forum is primarily for reporting robospam calls to block, I prefer not to comment here further about technical or legal solutions to robospam calls. That is for other Sonic forums. That said, you have enlightened me about the evolution of the technical issues with blocking robospam.