2 ms·

Okay we do the legwork and track him down. He's an Indian national using a stolen or prepaid credit card in Mumbai and using voip.ms or flowroute or whoever jus

Okay we do the legwork and track him down. He's an Indian national using a stolen or prepaid credit card in Mumbai and using voip.ms or flowroute or whoever just needs a CC to get started. He has long left this service and gone to another by the time you "catch" him. He's made millions of calls since.

MichaelGG 12y ago
Well most places don't just allow a credit card to start sending high volume, due to the fraud risk. But agreed, there may not be too much ID, and prosecuting internationally is hard. So there's a few options: 1. Don't allow such users to use other caller IDs until they verify themselves (business, USF ID, etc.) or until they verify ownership of the number, or some other limitation. This is fairly reasonable and can be totally automated (some providers do so). Some Indian shop doesn't need to spoof all US numbers, so why allow them? 2. Require deposits against such behavior, and in case of uncontested complaint, keep the money. 3. Share information on offenders (FCC run, mandatory). This is like having a list of known bad agents. Yes, they can get new IDs, but that costs a bit (see point 1, no need to allow someone in India on a free email account, without a company, impersonate all US numbers). 4. Of the FCC really wanted to nuke the problem, they could make providers liable. End of story. Within a month, providers would get together and figure it out. And this wouldn't need to hurt legitimate usage that much. Established operators are easy enough to figure out (or you can grandfather until there are complaints). End users trying to get going should have no problem, either.