VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
August 2018
- 23 participants
- 82 messages
LNP, tandems, etc.
by abalashov@evaristesys.com
On Wed, Aug 29, 2018 at 11:56:59AM -0500, BackUP Telecom Consulting wrote:
> However, if you have more than 24 DS0s worth of traffic to that small
> ILEC area, the small ILEC can force you to install a direct connection
> to them. That doesn't happen very often but I've seen it happen a few
> times.
Ah, you've reignited my nostalgia for flying-under-the-DEOTs adventures
of the managed modem boom...
Picking inbound up at the tandem from Tier 3+ / rural rate centres was
commonly done by CLECs providing managed modem. These were the kinds of
rate centres where the Level3s, Grandecoms, etc. of the world would not
go because there aren't enough ports, but there was enough traffic there
to constitute more than just the occasional call. Not coincidentally,
when broadband appeared, these places were the last to get it and
represented most of the lingering demand for dial-up, triggering a spike
in DEOT-related disputes.
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Aug. 29, 2018
LNP, tandems, etc.
by marylou@backuptelecom.com
If you have an LRN in the ILEC tandem provider's area, you can port
to/from any rate center in that ILEC area. If there are small ILECs that
use the big ILEC's tandem, you can also port to/from those rate centers.
However, if you have more than 24 DS0s worth of traffic to that small
ILEC area, the small ILEC can force you to install a direct connection
to them. That doesn't happen very often but I've seen it happen a few
times.
If you're using a third party provider like Inteliquent, you need to
have an LRN in every LATA that you want to port numbers in/out of. Your
traffic can traverse their network between LATAs through your one
connection with them, but in the background Inteliquent has to have
connections with each tandem provider in both areas in order for it to
work. That's why they give you a list of all the rate centers that they
cover when you sign up with them!
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=…
>
> LRN NPA-NXX in town B:
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
>
> 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
Aug. 29, 2018
LNP, tandems, etc.
by marylou@backuptelecom.com
That's true if the ILEC has an agreement with the tandem provider. There
are some little ILECs that have their own tandem and refuse to use the
big ILEC tandem provider! You have to look at the routing of the ILEC
switch in the LERG to figure that out.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-1111
On 2018-08-29 11:38 AM, Paul Timmins wrote:
> You don't actually have to establish connectivity to all ILECs in an
> area, even if you are porting out numbers from their ratecenters. The
> ILECs already have to have a way to reach any other tandem in the LATA
> so as long as you have an LRN homed on A tandem in the area, and port
> your numbers to that, you're good to go.
>
> The ILECs don't LIKE it, but if we cared what they truly liked we'd
> all just leave the market.
>
> On Aug 29, 2018 12:33, BackUP Telecom Consulting
> <marylou at backuptelecom.com> wrote:
>
> When there are multiple ILECs in a LATA like in LA - LATA 730, you
> would
> set up an interconnection point with each ILEC. So you'd have one for
> the AT&T areas and one for the old Verizon areas. When you have trunks
>
> to both carriers in the LATA, you can use your own network to switch
> traffic from the one LATA to the other LATA, but you can't deliver it
> to
> the ILEC and expect them to hand it off to the other ILEC. It would
> work
> the same with the third party providers.......as long as they have a
> connection in both ILEC areas, then they can use their own network to
> deliver the traffic from the one ILEC area to the other ILEC area.
>
> Mary Lou Carey
>
> BackUP Telecom Consulting
>
> Office: 615-771-7868 (temporary)
>
> Cell: 615-796-1111
>
> On 2018-08-28 08:18 PM, Mike Hammett wrote:
>> I thought everyone connected to the ILEC-hosted tandem responsible
> for
>> the rate centers where the number blocks were assigned, but that
> seems
>> to not always be the case when there are multiple ILEC-hosted
> tandems
>> in a LATA.
>>
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>
>> Midwest Internet Exchange
>> http://www.midwest-ix.com
>>
>> -------------------------
>>
>> FROM: "Erik" <erik at eespro.com>
>> TO: "Mike Hammett" <voiceops at ics-il.net>
>> CC: voiceops at voiceops.org
>> SENT: Tuesday, August 28, 2018 7:25:40 PM
>> SUBJECT: Re: [VoiceOps] LNP, tandems, etc.
>>
>> 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.
>>
>> On Tue, Aug 28, 2018 at 1:00 PM, 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
>>>
>>> -------------------------
>>>
>>> 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=…
> [1]
>>>
>>> LRN NPA-NXX in town B:
>>>
>>
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
> [2]
>>>
>>> Tandem in town B:
>>>
>>
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T
> [3]
>>> Tandem in town C:
>>>
>>
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T
> [4]
>>>
>>> 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
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> Links:
> ------
> [1]
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&excha…
> [2]
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&excha…
> [3]
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T
> [4]
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T
Aug. 29, 2018
LNP, tandems, etc.
by marylou@backuptelecom.com
It's true that in the metropolitan areas the ILECs will allow you to
trunk everything to the tandem, but the routing for rural areas is
handled totally different in some ILEC areas. The old CenturyLink used
to force carriers in some rural areas to deliver to the end office if
the office associated with the rate center because it was so far out
that the office had no local tandem. Others like the old Qwest
territories let you route all traffic from the switches that had no
local tandem over the Access Tandem if you had SPOP (Single Point of
Presence) language in your agreement. The old BellSouth areas let you
establish one Multi-tandem supergroup for the entire ILEC area and just
charged you minutes of use anytime they had to inter-tandem a call.
Every ILEC territory is just a little different, but they all share
commonalities that they require you to route the LRN NXX to the tandem
(or EO if there is no local tandem) that it is served by.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-1111
On 2018-08-28 07:25 PM, Erik wrote:
> 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.
>
> On Tue, Aug 28, 2018 at 1:00 PM, 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
>>
>> -------------------------
>>
>> 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=…
>> [1]
>> LRN NPA-NXX in town B:
>>
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
>> [2]
>> Tandem in town B:
>>
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T
>> [3]
>> Tandem in town C:
>>
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T
>> [4]
>>
>> 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 [5]
>
>
>
> Links:
> ------
> [1]
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&excha…
> [2]
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&excha…
> [3]
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T
> [4]
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILXA50T
> [5] https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 29, 2018
LNP, tandems, etc.
by marylou@backuptelecom.com
When there are multiple ILECs in a LATA like in LA - LATA 730, you would
set up an interconnection point with each ILEC. So you'd have one for
the AT&T areas and one for the old Verizon areas. When you have trunks
to both carriers in the LATA, you can use your own network to switch
traffic from the one LATA to the other LATA, but you can't deliver it to
the ILEC and expect them to hand it off to the other ILEC. It would work
the same with the third party providers.......as long as they have a
connection in both ILEC areas, then they can use their own network to
deliver the traffic from the one ILEC area to the other ILEC area.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-1111
On 2018-08-28 08:18 PM, Mike Hammett wrote:
> I thought everyone connected to the ILEC-hosted tandem responsible for
> the rate centers where the number blocks were assigned, but that seems
> to not always be the case when there are multiple ILEC-hosted tandems
> in a LATA.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> FROM: "Erik" <erik at eespro.com>
> TO: "Mike Hammett" <voiceops at ics-il.net>
> CC: voiceops at voiceops.org
> SENT: Tuesday, August 28, 2018 7:25:40 PM
> SUBJECT: Re: [VoiceOps] LNP, tandems, etc.
>
> 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.
>
> On Tue, Aug 28, 2018 at 1:00 PM, 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
>>
>> -------------------------
>>
>> 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=…
>>
>> LRN NPA-NXX in town B:
>>
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
>>
>> 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
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 29, 2018
LNP, tandems, etc.
by marylou@backuptelecom.com
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" <matthew at corp.crocker.com>
> TO: "Mike Hammett" <voiceops at ics-il.net>
> CC: voiceops at voiceops.org
> 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 <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>
>> TO: 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=…
>>
>> LRN NPA-NXX in town B:
>>
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
>>
>> 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
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
>> <LATA 364 Comcast LRN.png>
>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> Links:
> ------
> [1]
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILXA50T
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 29, 2018
LNP, tandems, etc.
by voiceops@ics-il.net
Are your LRNs homed off of the tandem switch traditionally responsible for the rate center in which the NPA-NXX your LRN is in?
IE: in my example picture, is your version of 815-901-0976 going to DKLBILXA50T or DIXNILXA50T?
-----
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: "Matthew S. Crocker" <matthew at corp.crocker.com>, voiceops at voiceops.org
Sent: Tuesday, August 28, 2018 10:40:40 PM
Subject: Re: [VoiceOps] LNP, tandems, etc.
For the same reason the ILEC gets to choose theirs. We're all independent networks and nobody is subordinate to anyone. I'm a big proponent of bypassing the ILEC at any opportunity, or using things like indirect interconnection to avoid needlessly purchasing transport hither and yon based on what some ILEC thought was a good idea in the 70s or 80s.
It takes a while to realize you can actually tell the ILEC what to do, but you can and it's kinda neat.
I have one LRN per LATA and it wouldn't make sense to do it any other way. Call rating is done based on the original dialed number and call routing is done off of the LRN.
On Aug 28, 2018 23:12, Mike Hammett <voiceops at ics-il.net> 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" <matthew at corp.crocker.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: voiceops at voiceops.org
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 < voiceops at ics-il.net > wrote:
<blockquote>
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 >
To: 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=…
LRN NPA-NXX in town B: https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
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
<blockquote>
<LATA 364 Comcast LRN.png>
</blockquote>
<blockquote>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
</blockquote>
</blockquote>
Aug. 29, 2018
LNP, tandems, etc.
by paul@timmins.net
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20180828/10f9bcad/at…>
Aug. 29, 2018
LNP, tandems, etc.
by voiceops@ics-il.net
I get that.
The LRN is out of an NPA-NXX assigned to a town off of the tandem I'm already connected to.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Erik" <erik at eespro.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "Paul Timmins" <paul at timmins.net>, voiceops at voiceops.org
Sent: Tuesday, August 28, 2018 8:34:57 PM
Subject: Re: [VoiceOps] LNP, tandems, etc.
Mike I think you are missing the bigger picture. The LRN is where the call goes thus it's where your transit fees will be. The phone number could be different or same lata but the LRN is what your switch is dialing
On Tue, Aug 28, 2018, 9:30 PM Mike Hammett < voiceops at ics-il.net > wrote:
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
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:
<blockquote>
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=…
LRN NPA-NXX in town B: https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
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
</blockquote>
Aug. 29, 2018
LNP, tandems, etc.
by voiceops@ics-il.net
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
----- Original Message -----
From: "Matthew Crocker" <matthew at corp.crocker.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: voiceops at voiceops.org
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 < 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
----- Original Message -----
From: "Mike Hammett" < voiceops at ics-il.net >
To: 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=…
LRN NPA-NXX in town B: https://www.telcodata.us/search-area-code-exchange-detail?npa=815&exchange=…
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
<blockquote>
<LATA 364 Comcast LRN.png>
</blockquote>
<blockquote>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
</blockquote>
Aug. 29, 2018