[VoiceOps] LNP, tandems, etc.

Matthew Crocker matthew at corp.crocker.com
Tue Aug 28 21:53:27 EDT 2018


Mike

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

On Aug 28, 2018, at 9:15 PM, Mike Hammett <voiceops at ics-il.net<mailto:voiceops at ics-il.net>> wrote:

I drew a picture, hoping it would clear things up a bit.

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.



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



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



________________________________
From: "Mike Hammett" <voiceops at ics-il.net<mailto:voiceops at ics-il.net>>
To: voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Sent: Tuesday, August 28, 2018 4:46:52 PM
Subject: [VoiceOps] LNP, tandems, etc.

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<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops

<LATA 364 Comcast LRN.png>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto: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/19f4c69b/attachment-0001.html>


More information about the VoiceOps mailing list