<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>Are your LRNs homed off of the tandem switch traditionally responsible for the rate center in which the NPA-NXX your LRN is in?<br><br>IE: in my example picture, is your version of 815-901-0976 going to DKLBILXA50T or DIXNILXA50T?<br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br><br><br>Midwest Internet Exchange<br>http://www.midwest-ix.com<br><br><span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Paul Timmins" <ptimmins@clearrate.com><br><b>To: </b>"Mike Hammett" <voiceops@ics-il.net><br><b>Cc: </b>"Matthew S. Crocker" <matthew@corp.crocker.com>, voiceops@voiceops.org<br><b>Sent: </b>Tuesday, August 28, 2018 10:40:40 PM<br><b>Subject: </b>Re: [VoiceOps] LNP, tandems, etc.<br><br>
<div dir="auto">
<div>For the same reason the ILEC gets to choose theirs. We're all independent networks and nobody is subordinate to anyone. I'm a big proponent of bypassing the ILEC at any opportunity, or using things like indirect interconnection to avoid needlessly purchasing
transport hither and yon based on what some ILEC thought was a good idea in the 70s or 80s.
<div dir="auto"><br>
</div>
<div dir="auto">It takes a while to realize you can actually tell the ILEC what to do, but you can and it's kinda neat.</div>
<div dir="auto"><br>
</div>
I have one LRN per LATA and it wouldn't make sense to do it any other way. Call rating is done based on the original dialed number and call routing is done off of the LRN.<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Aug 28, 2018 23:12, Mike Hammett <voiceops@ics-il.net> wrote:<br>
<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="font-family:'arial' , 'helvetica' , sans-serif;font-size:10pt;color:#000000">
Okay. I'll take that as my action item. On to the understanding...
<div><br>
<br>
<br>
I don't understand how someone can aribrarily choose which tandem an LRN hangs off of. Why aren't they forced to keep an LRN attached to whatever tandem handles a given incumbent rate center? In my situation, 815-901 is in DeKalb. DeKalb's tandem is... DeKalb.
How can Comcast decide to throw it onto Dixon's tandem? I wouldn't have this confusion if Comcast's LRN in Dixon was from an NPA-NXX assigned to Dixon.<br>
<br>
<div><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
http://www.ics-il.com<br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
http://www.midwest-ix.com<br>
<br>
<br>
</div>
<br>
<hr>
<div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:'helvetica' , 'arial' , sans-serif;font-size:12pt">
<b>From: </b>"Matthew Crocker" <matthew@corp.crocker.com><br>
<b>To: </b>"Mike Hammett" <voiceops@ics-il.net><br>
<b>Cc: </b>voiceops@voiceops.org<br>
<b>Sent: </b>Tuesday, August 28, 2018 8:53:27 PM<br>
<b>Subject: </b>Re: [VoiceOps] LNP, tandems, etc.<br>
<br>
<div></div>
<div>Mike</div>
<div><br>
</div>
<div>You either need to connect to the other tandem or pay another carrier to get you there. It is the responsibility of the originating carrier to get the call to the terminating carriers switch. Depending on the call volume you should probably just route
through your LD carrier</div>
<div><br>
On Aug 28, 2018, at 9:15 PM, Mike Hammett <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>> wrote:<br>
<br>
</div>
<blockquote>
<div>
<div style="font-family:'arial' , 'helvetica' , sans-serif;font-size:10pt;color:#000000">
I drew a picture, hoping it would clear things up a bit.<br>
<br>
Through my switch, we're trying to call a number in a block assigned to Sycamore, with an LRN in a DeKalb number block, but the common tandem operator is telling me that the LRN actually lives on a different tandem.<br>
<br>
<div><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
<a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a><br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
<a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a><br>
<br>
<br>
</div>
<br>
<hr>
<div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:'helvetica' , 'arial' , sans-serif;font-size:12pt">
<b>From: </b>"Mike Hammett" <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>><br>
<b>To: </b><a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br>
<b>Sent: </b>Tuesday, August 28, 2018 4:46:52 PM<br>
<b>Subject: </b>[VoiceOps] LNP, tandems, etc.<br>
<br>
<div style="font-family:'arial' , 'helvetica' , sans-serif;font-size:10pt;color:#000000">
I thought you had to be on the same tandem to port a number, but with what our tandem operator (Frontier) is telling me, this isn't the case.<br>
<br>
Comcast ported a number from us in town A. The LRN they pointed to is based in town B (per TelcoData). The tandem generally used by carriers in both towns is based in town B. Naturally, we send traffic to that tandem.<br>
<br>
The operator of that tandem is telling us that the LRN is actually homed off of a different tandem in our LATA (operated by CenturyLink) in town C. Unfortunately, I can't corroborate this information with TelcoData the only rate center I see off of that tandem
in TelcoData is an AT&T town next door.<br>
<br>
Where can I read up authoritatively on the porting requirements that would apply to this and related bits of info I should know?<br>
<br>
I'm checking on our LERG access as I know that has the authoritative information, but I don't have that access at the moment. Maybe we're not subscribed to it.<br>
<br>
Number NPA-NXX in town A: <a href="https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=991" target="_blank">https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=991</a>
<div>LRN NPA-NXX in town B: <a href="https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=901" target="_blank">https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=901</a></div>
<div>Tandem in town B: <a href="https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T" target="_blank">
https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T</a><br>
Tandem in town C: <a href="https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T" target="_blank">https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T</a><br>
<br>
<br>
Thanks.</div>
<div><br>
<div><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
<a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a><br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
<a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a><br>
<br>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">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>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote>
<div><LATA 364 Comcast LRN.png></div>
</blockquote>
<blockquote>
<div>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">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>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div><br></div></body></html>