The principle is valid; mobile numbers have HLRs. I would not exclude them or the method based on the free demo.
-----Original Message----- From: Paul Timmins [mailto:[email protected]] Sent: Friday, August 21, 2015 11:56 To: Hiers, David (DS) Cc: VoiceOps; [email protected] Subject: Re: [VoiceOps] Preventing calls to cell phones with guaranteed accuracy HLR Check doesn't know about my Sprint CDMA phone. On Aug 21, 2015 14:49, "Hiers, David" <[email protected]> wrote: > > Checking for the existence of TN’s HLR might do the trick: > > > > www.hlrcheck.com > > > > > > > > > > From: VoiceOps [mailto:[email protected]] On Behalf Of > Jared Geiger > Sent: Friday, August 21, 2015 11:40 > To: VoiceOps > Subject: Re: [VoiceOps] Preventing calls to cell phones with > guaranteed accuracy > > > > It seems ANI Networks has a product that would work. When you do an LRN dip, > it can show the OCN Category such as Cellular. Looks like it also supports > DNC list support. > > > > http://aninetworks.com/PDF/ANI_Networks_Routing_Registry_Service.pdf > > > > I don't have any experience with the product, but looks like this is what you > need. > > > > On Wed, Aug 19, 2015 at 4:25 PM, Carlos Alvarez <[email protected]> wrote: >> >> Their lists are already cleaned by NPA-NXX, it's just not sufficient any >> more because of LNP. Looks like the TCPA compliance product from Neustar, >> which someone else posted yesterday, is the best solution. Pretty cheap >> too. It's just indicates intermodal porting of a number with no other info. >> >> >> >> >> >> On Wed, Aug 19, 2015 at 12:40 PM Paul Timmins <[email protected]> wrote: >>> >>> I know a guy who runs a site that sells the npa nxx to carrier type at a >>> fraction of the lerg costs.... >>> >>> On Aug 19, 2015 11:39 AM, Alex Balashov <[email protected]> wrote: >>> > >>> > Indeed, you'd start from the NPAC, which would get you, for a given TN, >>> > an LRN. Then what? >>> > >>> > -- >>> > 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/ >>> > >>> > Sent from my BlackBerry. >>> > Original Message >>> > From: Kidd Filby >>> > Sent: Wednesday, August 19, 2015 10:52 >>> > To: Carlos Alvarez >>> > Cc: [email protected] >>> > Subject: Re: [VoiceOps] Preventing calls to cell phones with >>> > guaranteed accuracy >>> > >>> > If I were to offer this service or database access, I would start with my >>> > own local copy of NPAC that I'd update every X-minutes a day. This >>> > product is available now and has been for a while. This is the only >>> > sure-way, I know of, to have the most accurate data to work from. >>> > >>> > Kidd >>> > >>> > On Tue, Aug 18, 2015 at 2:30 PM, Carlos Alvarez <[email protected]> >>> > wrote: >>> > I have a customer in market research who is legally required to manually >>> > dial calls to cell phones. Right now they are considering abandoning all >>> > of their auto/predictive dialer software and going to manual dial for >>> > everything, because the list-scrubbing services have been shown to be >>> > inaccurate. There are extreme penalties for auto-dialing a cell phone, >>> > and "best effort" is NOT a defense to this, at all. For example, Gallup >>> > just settle a claim for $12M. >>> > >>> > So they need a totally accurate way to prevent a cell phone call from >>> > originating from their dialer. The only thing I can think of is some >>> > sort of LRN dip + LRN-to-carrier-type response. One of their people >>> > talked to Neustar, but didn't get great answers because he doesn't really >>> > understand telephony. Before I get in touch with Neustar, I thought I'd >>> > see if people here have some ideas. >>> > >>> > If you provide a commercial product for this, please feel free to tell me >>> > so on or off list, the customer is willing to pay for the service and >>> > we're open to all options. I don't have a budget number yet but manual >>> > dialing is going to cost them quite a bit for some types of studies. >>> > >>> > _______________________________________________ >>> > VoiceOps mailing list >>> > [email protected] >>> > https://puck.nether.net/mailman/listinfo/voiceops >>> > >>> > >>> > -- >>> > Kidd Filby >>> > 661.557.5640 (C) >>> > http://www.linkedin.com/in/kiddfilby >>> > >>> > _______________________________________________ >>> > VoiceOps mailing list >>> > [email protected] >>> > https://puck.nether.net/mailman/listinfo/voiceops >>> _______________________________________________ >>> VoiceOps mailing list >>> [email protected] >>> https://puck.nether.net/mailman/listinfo/voiceops >> >> >> _______________________________________________ >> VoiceOps mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/voiceops > > > > ________________________________ > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, notify the sender immediately by return > email and delete the message and any attachments from your system. _______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
