<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<style type="text/css">.mceResizeHandle {position: absolute;border: 1px solid black;background: #FFF;width: 5px;height: 5px;z-index: 10000}.mceResizeHandle:hover {background: #000}img[data-mce-selected] {outline: 1px solid black}img.mceClonedResizable, table.mceClonedResizable {position: absolute;outline: 1px dashed black;opacity: .5;z-index: 10000}
.mceResizeHandle {position: absolute;border: 1px solid black;background: #FFF;width: 5px;height: 5px;}
.mceResizeHandle:hover {background: #000;}
img[data-mce-selected] {}
img.mceClonedResizable, table.mceClonedResizable {position: absolute;}
</style></head><body style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><div>It's in LERG 6.</div>
<div> </div>
<div>NPAC is used to associate the TN to the LRN so it can go to the right carrier. They have no concern what type of call it is other than which databases it should be dipped from. The LERG is the authority on routing so that's the one you'll have to look in. Also, each thousand can be different so you can't just pull by A block. I would pull LERG 6 data and map it to the LRN from LERG 12 by associating the switch in both. LERG 6 has multiple switch homing arrangements, but all LRNs from the same NPA-NXX will have the same homing arrangement.</div>
<div> </div>
<div>Mary Lou Carey</div>
<div>BackUP Telecom Consulting</div>
<div>615-791-9969</div>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">On August 19, 2015 at 1:09 PM Alex Balashov <abalashov@evaristesys.com> wrote:<br><br>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;">Thanks, Mary Lou. But does the NPAC have any such fields as well?</div>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;"> </div>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;">Incidentally, where are the COCTYPE/SSC/COTYPE fields in the LERG? I was just getting the operator designation from LERG1, and mapping LRNs from LERG12.</div>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;">. </div>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;">Keep in mind I'm viewing lergdata.mdb on Linux, and that's an enormous pain and doesn't lend itself to easy exploration. :-)</div>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;"><span> </span></div>
<div style="width: 100%; font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;"><span>--</span></div>
<div style="font-family: Calibri, 'Slate Pro', sans-serif; color: #1f497d; background-color: #ffffff;">Alex Balashov | Principal | Evariste Systems LLC<br>303 Perimeter Center North, Suite 300<br>Atlanta, GA 30346<br>United States<br><br>Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)<br>Web: http://www.evaristesys.com/, http://www.csrpswitch.com/<br><br>Sent from my BlackBerry.</div>
<table style="border-spacing: 0px; width: 100%; background-color: white;">
<tbody>
<tr>
<td style="background-color: #ffffff;" colspan="2">
<div style="border-style: solid none none; border-top-color: #b5c4df; border-top-width: 1pt; padding: 3pt 0in 0in; font-family: Tahoma, 'BB Alpha Sans', 'Slate Pro'; font-size: 10pt;">
<div><strong>From: </strong>Mary Lou Carey</div>
<div><strong>Sent: </strong>Wednesday, August 19, 2015 13:59</div>
<div><strong>To: </strong>Alex Balashov; James Milko</div>
<div><strong>Reply To: </strong>Mary Lou Carey</div>
<div><strong>Cc: </strong>VoiceOps</div>
<div><strong>Subject: </strong>Re: [VoiceOps] Preventing calls to cell phones with guaranteed accuracy</div>
</div>
</td>
</tr>
</tbody>
</table>
<div style="border-style: solid none none; border-top-color: #babcd1; border-top-width: 1pt; background-color: #ffffff;"> </div>
<br>
<div id="_originalContent">
<div>I am an AOCN and yes the LERG has fields that differentiates between wireline and wireless. There are actually three fields that you could filter by:</div>
<div> </div>
<div>COCTYPE: Identifies the type of code</div>
<div>SSC: Identifies the type of service</div>
<div>COTYPE: Identifies the type of carrier</div>
<div> </div>
<div>Mary Lou Carey</div>
<div>BackUP Telecom Consulting</div>
<div>615-791-9969</div>
<div> </div>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">On August 19, 2015 at 12:32 PM James Milko <jmilko@bandwidth.com> wrote:<br><br>
<div dir="ltr">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.
<div><br>
<div class="gmail_extra">
<div>
<div class="gmail_signature">
<div dir="ltr">
<p style="margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13px; font-family: Arial; color: #999999; background-color: #ffffff; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">James Milko</span><span style="font-size: 13px; font-family: Arial; color: #999999; background-color: #ffffff; font-weight: normal; font-style: italic; font-variant: normal; text-decoration: none; vertical-align: baseline;"></span></p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13px; font-family: Arial; color: #999999; background-color: #ffffff; font-weight: normal; font-style: italic; font-variant: normal; text-decoration: none; vertical-align: baseline;">Architect, Network Engineering<br></span></p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13px; font-family: Arial; color: #888888; background-color: #ffffff; font-weight: normal; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">900 Main Campus Drive</span></p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13px; font-family: Arial; color: #888888; background-color: #ffffff; font-weight: normal; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Raleigh, NC 27606</span><span style="font-size: 13px; font-family: Arial; color: #999999; background-color: #ffffff; font-weight: normal; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;"></span></p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"><a href="http://www.bandwidth.com/business/" target="_blank"><span style="font-size: 13px; font-family: Arial; color: #1962cf; background-color: #ffffff; font-weight: normal; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">Bandwidth</span></a><span style="font-size: 13px; font-family: Arial; color: #1962cf; background-color: #ffffff; font-weight: normal; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;"></span></p>
<p style="margin-top: 0pt; margin-bottom: 0pt;"> </p>
</div>
</div>
</div>
<div class="gmail_quote">On Wed, Aug 19, 2015 at 11:39 AM, Alex Balashov <span><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">Indeed, you'd start from the NPAC, which would get you, for a given TN, an LRN. Then what?<br> <br> <span>--<br> Alex Balashov | Principal | Evariste Systems LLC<br> 303 Perimeter Center North, Suite 300<br> Atlanta, GA 30346<br> United States<br> <br> Tel: <a>+1-800-250-5920</a> (toll-free) / <a>+1-678-954-0671</a> (direct)<br> Web: <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" target="_blank">http://www.csrpswitch.com/</a><br> <br> </span>Sent from my BlackBerry.<br> Original Message <br> From: Kidd Filby<br> Sent: Wednesday, August 19, 2015 10:52<br> To: Carlos Alvarez<br> Cc: <a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a><br> <span class="im HOEnZb">Subject: Re: [VoiceOps] Preventing calls to cell phones with guaranteed accuracy<br> <br> </span>
<div class="HOEnZb">
<div class="h5">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.<br> <br> Kidd<br> <br> On Tue, Aug 18, 2015 at 2:30 PM, Carlos Alvarez <<a href="mailto:caalvarez@gmail.com">caalvarez@gmail.com</a>> wrote:<br> 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.<br> <br> 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.<br> <br> 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.<br> <br> <br> _______________________________________________<br> VoiceOps mailing list<br> <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br> <a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br> <br> <br> <br> <br> --<br> Kidd Filby<br> <a>661.557.5640</a> (C)<br> <a href="http://www.linkedin.com/in/kiddfilby" target="_blank">http://www.linkedin.com/in/kiddfilby</a><br> <br> _______________________________________________<br> VoiceOps mailing list<br> <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br> <a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>VoiceOps mailing list<br>VoiceOps@voiceops.org<br>https://puck.nether.net/mailman/listinfo/voiceops</blockquote>
<div><br> </div>
Mary Lou Carey<br>BackUP Telecom Consulting<br>Marylou@backuptelecom.com<br>Office: 615-791-9969<br>Cell: 615-796-1111<br><!--end of _originalContent --></div>
</blockquote>
<div><br> </div>
<blockquote type="cite" style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;">_______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops</blockquote>
<div><br> </div>
Mary Lou Carey<br>BackUP Telecom Consulting<br>Marylou@backuptelecom.com<br>Office: 615-791-9969<br>Cell: 615-796-1111</body></html>