[VoiceOps] LNP, tandems, etc.

Tue Aug 28 21:30:30 EDT 2018

It may very well be that it's cheaper to dump calls off to a termination provider (or Inteliquent) instead of getting myself over to the other tandem. I just want to make sure that I have to build it (or sub it out to the previously mentioned) and not make my current tandem operator haul it. 

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

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

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

From: paul at timmins.net 
To: voiceops at ics-il.net, voiceops at voiceops.org 
Cc: voiceops at voiceops.org 
Sent: Tuesday, August 28, 2018 7:24:47 PM 
Subject: Re: [VoiceOps] LNP, tandems, etc. 

There's a lot going on here and I'm on a cellphone on vacation but you need _A_ way to reach the tandem. You don't need direct connectivity, and you don't need bidirectional connectivity. I've terminated calls to rural CenturyLink ilec via global crossing wholesale long distance because it was cheaper than maintaining an unnecessary tandem connection to wherever that thing was hooked given we had so few calls. I later negotiated an ICA with them that allowed for that to continue while we ported numbers away from them, since they could reach the tandem we were at. 

I wish I could draw the diagram this deserves but right now my most realistic tool is a stick and mud to draw it so maybe another time on that. :) 

On Aug 28, 2018 19:00, Mike Hammett <voiceops at ics-il.net> 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 

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

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 

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