It could be anytime the *LEC still has the entire A block. As far as how common it is I can't really say. My cell phone and childhood phone number are both native routed.
Wireline: http://www.localcallingguide.com/lca_prefix.php?npa=732&nxx=363 Wireless: http://www.localcallingguide.com/lca_prefix.php?npa=201&nxx=320 James Milko Architect, Network Engineering 900 Main Campus Drive Raleigh, NC 27606 Bandwidth <http://www.bandwidth.com/business/> On Wed, Aug 19, 2015 at 1:39 PM, Alex Balashov <[email protected]> wrote: > Aren't 95%+ rate centres pooled these days? If so, they'd still have > LRNs, since LRN-guided routing is a requirement of pooling. So, who still > has non-pooled 10K blocks? Is that common in metro, or largely a trait of > rural LECs? > > -- > 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. > *From: *James Milko > *Sent: *Wednesday, August 19, 2015 13:32 > *To: *Alex Balashov > *Cc: *VoiceOps > *Subject: *Re: [VoiceOps] Preventing calls to cell phones with guaranteed > accuracy > > NPAC has a service type field that indicates wireless/wireline. That > doesn't solve for native numbers though since they won't have LRN data > since they don't have LRNs. I don't remember offhand if LERG has a > wireless/wireline indication for a given [A]OCN or block. > > James Milko > > Architect, Network Engineering > > 900 Main Campus Drive > > Raleigh, NC 27606 > > Bandwidth <http://www.bandwidth.com/business/> > > > On Wed, Aug 19, 2015 at 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
