[VoiceOps] Preventing calls to cell phones with guaranteed accuracy
Carlos Alvarez
caalvarez at gmail.com
Fri Aug 21 16:15:05 EDT 2015
That's all we need to know. If the number is currently going to a cell
carrier, it gets moved to a manual-dial bucket. If not, allow it to be
auto-dialed. That's all. The regulations are a joke and are just
affecting legit businesses doing actual work. The spam/scam operators just
ignore it all and can't be found since they are overseas or using overseas
proxies.
I've since also found, from my own research, that there are many reasons
they could still auto-dial a cell phone. If they have any existing
business with the person, if the person has previously agreed to do phone
surveys, and similar scenarios. So the only numbers affected are those
that they random-dial or sequential-dial for purposes of polling a random
sampling of people. This is only a small fraction of their projects.
On Fri, Aug 21, 2015 at 12:41 PM Alex Balashov <abalashov at evaristesys.com>
wrote:
> Why should Carlos's client care about HLR DB entries? Isn't determining
> whether the number is homed to a mobile operator sufficient to indemnify
> against the regulation?
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
> 303 Perimeter Center North, Suite 300
> Atlanta, GA 30346
> United States
>
> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20150821/6fb1d630/attachment.html>
More information about the VoiceOps
mailing list