Upgrade callerID to use ANI or some other tech to prevent it from being spoofed or blocked; so we can find the bastards.
ANI would be awful to use as a callerID because it marks signals the calling service line billing number. When you have a PRI/DS3/etc service trunk, the ANI for all calls out is that service trunk number, even though you may have thousands of legitimate TNs/callerIDs on the trunk.
I run more than a dozen PBXs hanging off a DS3 and multiple PRI trunks, thousands of incoming TN destinations, plus a fee hundred more valid outgoing TNs (think local business offices, outgoing calls with callerID of corporate main or 800 number). The ANI for all these outgoing call is the billing number of the trunk the call goes out.... It represents the responsible billing/legal party for escalation, not the actual endpoint calling. Further... ANI can be spoofed as well. It is much harder to (generally requires an SS7 trunk, which smaller companies dontt generally have access too), but can be spoofed the same.
The problem is not callerID perse, it is that the telcos refuse to filter/identify/track ongoing fraudulent uses of callerID on their network. The telco can easily pull their internal call records, lookup the ANI and routing codes associated with an incoming call, and track that call back thru their systems to the source. We have had repeated problems with dead-air callers to 800 voice numbers (apparently fax spammers) that come in burts from rotating sets of valid but fraudulent callerIDs. (Over days/weeks I have been able to capture the list and then predict the next incoming fraudulent callerID). I have sat on the phone with telco techs as they ran thru my call log of fraudulent callerIDs and confirmed the call path/ANI did not match that of what the presented callerID would have... But the telcos seem to have a policy that they will not investigate or stop the activity until sued in a specific case.
Remove the exemption for charity and political fundraisers and pollsters. Remove the "existing relationship" loophole so that when you add your number the calls STOP unless you explicitly exempt them (And that exemption should be revocable.).
The charity/political exemption is not going away, that is a pipe dream... As for "existing relationships", you can already tell a caller to stop calling you and they must add you to their internal do-not-call list. What needs to be added to the "existing relationship" loophole is a specification that "existing relationship" only applies to existing services between you and the caller and specifically excludes the business or "partners" for calling in references to new services.
Remove the 31-day wait when a number is added (Seriously, WTF? I'm not buying a gun here. I don't need a cooling-off period.
It is not a cooling off period and the 31-day wait is not for your benefit. It is a time frame so the hundreds of thousands of users of the do-no-call list can update their systems (which they are required to do at least once every 30 days). Sorry if you believe this stuff magically happens "in the cloud" instantly... but not everything is instant. It takes actual time and manpower to cross-reference databases, build filtering rules, and upload data sets to equipment. Quality calling centers are updating their do-not-call list every week, smaller call centers every few weeks. Can you guess how often the fraudulent callerID callers update their do-not-call list?
But none of this really applies... In my experience, the vast majority of do-not-call list violations are already illegal to begin with. When you get a "Card Holder Services" call, it is never CHS, it is one of dozens/hundreds of different groups using the name and making fraudulent/criminal calls. As is the same for the "You have won a free cruise", "You have qualified to reduce/refinance your student loans", etc...