<div dir="ltr"><div class="gmail_extra">Most providers simply connect to the tandem at the ILEC. The end office transit termination and origination cost is SO LOW that it doesn't make since to have a switch or access point at the end office. Since most things are ILEC if not all are VOIP everything is coming from a centralize switch point. Hopefully all the 1970's billing methods will disappear.</div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Tue, Aug 28, 2018 at 1:00 PM, Mike Hammett <span dir="ltr"><<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>></span> wrote:<br><blockquote class="gmail_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">Meaning if I thought were true? I had just assumed that Inteliquent did have the connections to every tandem in the LATAs they serve, given that (my thought) that you could only port numbers on the same tandem, so universal coverage would require connections to every tandem. We're actually looking at someone like Inteliquent to expand our footprint.<br><br>So I'm supposed to be connected to every tandem in my LATA? In my LATA, there are only two (I believe), but some LATAs (like Chicago) have several. I'm supposed to drag a DS1 (or use Inteliquent, etc. if available) to connect to each one, even if I don't provide service in the rate centers traditionally served by that tandem? It seems like Comcast threw a dart at a dart board in choosing which tandem to connect to vs. going with the one that everyone else in that town uses.<br><br>So then I could port a number from any rate center in my LATA (say Savanna) and point it to my LRN, living off of a tandem switch that the Savanna ILEC isn't connected to (from my outside world perspective)? Is there even the LATA constraint? Given the porting limitations I had experienced in the VoIP world, I assumed it was a tandem-by-tandem basis.<br><br>So the LERG shows which tandem I need to send traffic to if I want to talk to them, but they could send their outbound calls to a different tandem? My current customer complaint is for calls that we're sending to Comcast, apparently homed off of the other tandem.<br><br>If everyone is supposed to be on every tandem, then why can't the tandem I'm on just accept the calls I'm sending to Comcast, since Comcast should be there? Obviously me not being on the other tandem would affect inbound traffic to me.<br><br>Is there another service I should be paying Frontier for to get me to the other tandem with some value-add service? I know CenturyLink hops through almost every town going that way (former LightCore and others before route). Frontier or CenturyLink may be able to get me a DS1 to the other tandem if I need that.<br><br><br>I'm aware that I could still be completely missing the mark.<br><br><br><br>BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't for many ages.<span class=""><br><br><div><span name="x"></span><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><span name="x"></span><br></div><br></span><hr id="m_8533095475297467796zwchr"><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" <<a href="mailto:ptimmins@clearrate.com" target="_blank">ptimmins@clearrate.com</a>><br><b>To: </b>"Mike Hammett" <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>><br><b>Cc: </b><a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br><b>Sent: </b>Tuesday, August 28, 2018 5:19:11 PM<br><b>Subject: </b>Re: [VoiceOps] LNP, tandems, etc.<br><br>
<div dir="auto">If that were true, you wouldn't be able to use inteliquent (et al) as your access tandem. Everyone is supposed to be directly or indirectly connected to every tandem in the LATA (which you can't independently verify, as telcodata and the LERG
both show terminating tandem information to reach that end office, not what tandems the end office is hooked to to terminate calls.</div><div><div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Aug 28, 2018 17:47, Mike Hammett <<a href="mailto:voiceops@ics-il.net" target="_blank">voiceops@ics-il.net</a>> wrote:<br>
</div>
</div>
<div>
<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/<wbr>search-area-code-exchange-<wbr>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/<wbr>search-area-code-exchange-<wbr>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/<wbr>search-switches-by-tandem-<wbr>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/<wbr>search-switches-by-tandem-<wbr>clli?cllicode=DIXNILXA50T</a><br>
<br>
<br>
Thanks.</div>
<div><br>
<div><span></span><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>
<span></span><br>
</div>
</div>
</div>
</div>
</div></div></div><br></div></div><br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div></div>