You can pick which rate center your LRN will be assigned from, but you
still have to follow the tandem homing established by the ILEC for that
rate center. Not all ILECs require the same type of trunking to each of
the tandems, but all require you to home your LRN on the tandem that
your LRN-NXX would normally be served by in the PSTN network. Now you
can appear to get around this by using the CLLI code of a third party
providers, but the third party providers network is required to route
traffic like the ILEC so really you're just using one pipe to send all
your traffic to the ILEC and the third party provider breaks it out
according to what tandem the ILEC requires trunking to.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-1111
On 2018-08-28 09:56 PM, Mike Hammett wrote:
Okay. I'll take that as my action item. On to the understanding...
I don't understand how someone can aribrarily choose which tandem an
LRN hangs off of. Why aren't they forced to keep an LRN attached to
whatever tandem handles a given incumbent rate center? In my
situation, 815-901 is in DeKalb. DeKalb's tandem is... DeKalb. How
can Comcast decide to throw it onto Dixon's tandem? I wouldn't have
this confusion if Comcast's LRN in Dixon was from an NPA-NXX assigned
to Dixon.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
-------------------------
FROM: "Matthew Crocker" <[email protected]>
TO: "Mike Hammett" <[email protected]>
CC: [email protected]
SENT: Tuesday, August 28, 2018 8:53:27 PM
SUBJECT: Re: [VoiceOps] LNP, tandems, etc.
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 <[email protected]> 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" <[email protected]>
TO: [email protected]
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
[1]
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
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
<LATA 364 Comcast LRN.png>
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
Links:
------
[1]
https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
