<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'>I reached out to Comcast and pending an increase in installed trunk capacity, they should have the problem fixed by next month. I'd imagine if Frontier installed the new trunks faster than allowed by the tariff, Comcast would have it resolved more quickly.<br><br>By fixed, I mean Comcast is moving their LRN back to the correct tandem.<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>"Mike Hammett" <voiceops@ics-il.net><br><b>To: </b>voiceops@voiceops.org<br><b>Sent: </b>Tuesday, August 28, 2018 4:46:52 PM<br><b>Subject: </b>[VoiceOps] LNP, tandems, etc.<br><br><style>p { margin: 0; }</style><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: https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=991<div>LRN NPA-NXX in town B: https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=901</div><div>Tandem in town B: https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T<br>Tandem in town C: https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T<br><br><br>Thanks.</div><div><br><div><span></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></span><br></div></div></div><br>_______________________________________________<br>VoiceOps mailing list<br>VoiceOps@voiceops.org<br>https://puck.nether.net/mailman/listinfo/voiceops<br></div><br></div></body></html>