[VoiceOps] LNP, tandems, etc.

Wed Aug 29 15:33:19 EDT 2018

So then as someone fairly new to the telco side (brief run down of how things worked fifteen years ago, then moved on to IP, microwave, etc. to avoid regulatory nightmares... now responsible for the operations of a company doing each part themselves), my confusion is understandable? 

Understood on the > 24 DS0s part. We have some DS1s to specific towns in addition to the tandem connection. 

If I were working with rate centers off of the other tandem, having a connection to the other tandem makes sense. However, my only dealings with that other tandem is that Comcast moved their LRN over there. 

I'll reach out to Frontier and see what we can do. 

----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest Internet Exchange 
http://www.midwest-ix.com 

----- Original Message -----

From: "BackUP Telecom Consulting" <marylou at backuptelecom.com> 
To: "Mike Hammett" <voiceops at ics-il.net> 
Cc: voiceops at voiceops.org 
Sent: Wednesday, August 29, 2018 1:34:18 PM 
Subject: Re: [VoiceOps] LNP, tandems, etc. 

I am an AOCN and have real time access to the LERG so just out of 
curiosity and because I like mysteries, I looked up your example to see 
what you were talking about. Comcast's records in LATA 364 are a mess! 

Most of Comcast's NXXs were assigned back in 11/07/13. When it was 
originally added, Comcast had it homed on the DKLBILXA50T tandem, which 
is correct. Then in February 2016 someone made a SHA change to their 
switch record and changed the tandem to DIXNILXA50T for the Local and 
IntraLATA tandems and CHCGILWU24T for the FGD Tandem. My guess is that 
Comcast initially set it up correctly, but when they added the 
CenturyLink territory of the LATA, they didn't add a second switch 
homing arrangement and LRN for the CenturyLink territory like they 
should have. I can't explain why it works unless there just haven't been 
any new companies since 2016. I would call Frontier back and tell them 
that they must have trunks established with Comcast because they have a 
bunch of NXXs in their territory that were set up in November 2013. 

Mary Lou Carey 

BackUP Telecom Consulting 

Office: 615-771-7868 (temporary) 

Cell: 615-796-1111 

On 2018-08-28 06:00 PM, Mike Hammett wrote: 
> 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. 
> 
> 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. 
> 
> 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. 
> 
> 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. 
> 
> 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. 
> 
> 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. 
> 
> I'm aware that I could still be completely missing the mark. 
> 
> BTW: Thanks for TelcoData. I subscribed a long time ago, but haven't 
> for many ages. 
> 
> ----- 
> Mike Hammett 
> Intelligent Computing Solutions 
> http://www.ics-il.com 
> 
> Midwest Internet Exchange 
> http://www.midwest-ix.com 
> 
> ------------------------- 
> 
> FROM: "Paul Timmins" <ptimmins at clearrate.com> 
> TO: "Mike Hammett" <voiceops at ics-il.net> 
> CC: voiceops at voiceops.org 
> SENT: Tuesday, August 28, 2018 5:19:11 PM 
> SUBJECT: Re: [VoiceOps] LNP, tandems, etc. 
> 
> 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. 
> 
> On Aug 28, 2018 17:47, Mike Hammett <voiceops at ics-il.net> wrote: 
> 
> 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. 
> 
> 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. 
> 
> 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. 
> 
> Where can I read up authoritatively on the porting requirements that 
> would apply to this and related bits of info I should know? 
> 
> 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. 
> 
> Number NPA-NXX in town A: 
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=991 
> 
> LRN NPA-NXX in town B: 
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=901 
> 
> Tandem in town B: 
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T 
> Tandem in town C: 
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T 
> 
> Thanks. 
> 
> ----- 
> Mike Hammett 
> Intelligent Computing Solutions 
> http://www.ics-il.com 
> 
> Midwest Internet Exchange 
> http://www.midwest-ix.com 
> _______________________________________________ 
> VoiceOps mailing list 
> VoiceOps at voiceops.org 
> https://puck.nether.net/mailman/listinfo/voiceops 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20180829/bf257808/attachment.html>