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 2019
- 16 participants
- 36 messages
Connecting to Remote Tandems
by voiceops@ics-il.net
*nods* If I'm not using a third party tandem provider for the local tandem, then I have to build it myself (whether it's actual collocation or just dropping trunks on some transport provider). Since I already did all of that work, why have that third party do the access tandem... since I'm already there anyway. That product just doesn't make a lot of sense to me.
I do understand that they would have higher costs in some (even many) scenarios, simply by adding me as a customer. The commercial terms for the two types of service were as different as unicorns and lollipops. That's why I assumed things must be critically different... or they just aren't competitive on that product and someone else is.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Mary Lou Carey" <marylou at backuptelecom.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "VoiceOps" <voiceops at voiceops.org>
Sent: Friday, August 9, 2019 3:14:38 PM
Subject: Re: [VoiceOps] Connecting to Remote Tandems
There are a couple differences for various reasons. In the LERG there
are actually 3 tandems listed: One for Local, One for IntraLATA, and one
for FGD traffic. When you interconnect with only the ILEC, they only
have you establish 2 trunk groups. A local tandem trunk group that
handles the Local and IntraLATA traffic, and an Access Tandem trunk
group that handles the transit traffic you and the IXC carriers. When
you are connected to the ILEC, all 3 tandem offices in the LERG are
listed as the ILECs tandems.
If you hire a third party tandem provider for just "access traffic",
you're only changing that FGD tandem so the only trunk group you are
eliminating with the ILEC is the Access Tandem Trunk group.
If you're going to have a third party tandem provider handle your local
and IntraLATA traffic as well as your FGD traffic, then the LERG records
change significantly. Instead of using your own switch CLLI, you get a
POI CLLI for the LATA and populate the third party tandem provider's
switch CLLI in the actual switch field of the LERG. This tells everyone
that the NXXs belong to your company, but you're leasing another
company's switch to handle all the routing. This service eliminates the
need for all dedicated trunks between you and the ILEC so you just have
trunks between you and the third party tandem.
However, there is one more caveat and that is that it depends on what
ILEC you are interconnecting with. Verizon will allow the 3rd party
tandem provider to add your company's NXXs onto their existing trunk
group. CenturyLink and AT&T do not do that. They require the third party
tandem providers to install a dedicated trunk group for each company
that they are providing switching service for. Because a dedicated trunk
group between them and the ILEC costs them more, they will bill you
differently in those areas.
So the upside to having a third party tandem provider for Local
IntraLATA traffic is that you don't have to manage the Local IntraLATA
trunks yourself. The downside is that you probably will pay more per
minute if you send the traffic through the third party tandem provider.
Make sense?
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2019-08-09 02:42 PM, Mike Hammett wrote:
> I'm evaluating methods of extending our footprint. I purposely left
> out company names.
>
> One of the companies we talked to was really only interested in
> getting us the inbound long distance calls, not the local ones. Well,
> they would, but the terms were vastly different.
>
> Given that I still need to build out to connect to the local tandem,
> what's the point in using a third party to connect to long distance?
>
> Are the terms for connecting to the local tandems different because
> the access tandem is simpler, whereas the local tandem could
> potentially involve connections to a bunch of other switches, once
> volume dictated I needed direct connections... and they don't want to
> deal with that?
>
> Are there third parties that don't have vastly different terms for
> local tandem services?
>
> Also, is it likely that I just don't understand what's going on? I
> went circles with the sales rep to make sure I understood what he was
> saying, but I could be wrong.
>
> -----
> 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. 9, 2019
Connecting to Remote Tandems
by voiceops@ics-il.net
In our home turf, the same entity is operating local and long distance tandems (I hear it's even the same chassis, just a different blade), so locally, I wouldn't really be avoiding dealing with the ILEC. I understand that may not always be the case. I'd assume it would be fairly common, though, where one ILEC is dominate in the LATA.
Ah, so scale doesn't necessarily help them on the local side if I need all of my own trunks anyway. That makes sense. The terms presented to me don't seem to jive well with (my portion of costs of the other gear + profit) * number of trunks required, but that could be a business decision on their side.
It totally makes sense that the incumbent and\or government are the source of the problems and not some third party trying to solve problems and provide a service.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Paul Timmins" <paul at timmins.net>
To: voiceops at voiceops.org
Sent: Friday, August 9, 2019 2:51:41 PM
Subject: Re: [VoiceOps] Connecting to Remote Tandems
I'm sure I know which one you're talking about. It's because they exist in entirely different regulatory domains. The upside of inbound feature group D is that you get to cut out a terrible ILEC tandem, and at least the vendor I'm thinking of doesn't charge for the trunks themselves, so you're at a very strong cost advantage on it.
Inbound local trunking, usually interconnection agreements dictate that the trunks have to be dedicated per carrier, so you're just avoiding sinking hardware cost and transport, but it still uses up considerable resources at least in AT&T areas. So if you need 3 trunks to CHCGILWB's tandem, they can't just route that to their trunks where they have existing capacity, like FGD, but they have to install 3 shiny new T1s just for your traffic, that they order as you, to their equipment. It's stupid, convoluted, and wasteful but it's not the vendor's fault, it's AT&T maintaining artificial barriers to competition. As if they'd have it any other way.
-Paul
On 8/9/19 3:42 PM, Mike Hammett wrote:
I'm evaluating methods of extending our footprint. I purposely left out company names.
One of the companies we talked to was really only interested in getting us the inbound long distance calls, not the local ones. Well, they would, but the terms were vastly different.
Given that I still need to build out to connect to the local tandem, what's the point in using a third party to connect to long distance?
Are the terms for connecting to the local tandems different because the access tandem is simpler, whereas the local tandem could potentially involve connections to a bunch of other switches, once volume dictated I needed direct connections... and they don't want to deal with that?
Are there third parties that don't have vastly different terms for local tandem services?
Also, is it likely that I just don't understand what's going on? I went circles with the sales rep to make sure I understood what he was saying, but I could be wrong.
-----
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. 9, 2019
Connecting to Remote Tandems
by marylou@backuptelecom.com
I forgot to mention one more thing......if the third party tandem
provider is handling the local and intraLATA traffic for you as well as
the FGD traffic, then you don't have to mess with managing your own SS7
network or programming your switch for the PSTN routing.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2019-08-09 03:14 PM, Mary Lou Carey wrote:
> There are a couple differences for various reasons. In the LERG there
> are actually 3 tandems listed: One for Local, One for IntraLATA, and
> one for FGD traffic. When you interconnect with only the ILEC, they
> only have you establish 2 trunk groups. A local tandem trunk group
> that handles the Local and IntraLATA traffic, and an Access Tandem
> trunk group that handles the transit traffic you and the IXC carriers.
> When you are connected to the ILEC, all 3 tandem offices in the LERG
> are listed as the ILECs tandems.
>
> If you hire a third party tandem provider for just "access traffic",
> you're only changing that FGD tandem so the only trunk group you are
> eliminating with the ILEC is the Access Tandem Trunk group.
>
> If you're going to have a third party tandem provider handle your
> local and IntraLATA traffic as well as your FGD traffic, then the LERG
> records change significantly. Instead of using your own switch CLLI,
> you get a POI CLLI for the LATA and populate the third party tandem
> provider's switch CLLI in the actual switch field of the LERG. This
> tells everyone that the NXXs belong to your company, but you're
> leasing another company's switch to handle all the routing. This
> service eliminates the need for all dedicated trunks between you and
> the ILEC so you just have trunks between you and the third party
> tandem.
>
> However, there is one more caveat and that is that it depends on what
> ILEC you are interconnecting with. Verizon will allow the 3rd party
> tandem provider to add your company's NXXs onto their existing trunk
> group. CenturyLink and AT&T do not do that. They require the third
> party tandem providers to install a dedicated trunk group for each
> company that they are providing switching service for. Because a
> dedicated trunk group between them and the ILEC costs them more, they
> will bill you differently in those areas.
>
> So the upside to having a third party tandem provider for Local
> IntraLATA traffic is that you don't have to manage the Local IntraLATA
> trunks yourself. The downside is that you probably will pay more per
> minute if you send the traffic through the third party tandem
> provider. Make sense?
>
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2019-08-09 02:42 PM, Mike Hammett wrote:
>> I'm evaluating methods of extending our footprint. I purposely left
>> out company names.
>>
>> One of the companies we talked to was really only interested in
>> getting us the inbound long distance calls, not the local ones. Well,
>> they would, but the terms were vastly different.
>>
>> Given that I still need to build out to connect to the local tandem,
>> what's the point in using a third party to connect to long distance?
>>
>> Are the terms for connecting to the local tandems different because
>> the access tandem is simpler, whereas the local tandem could
>> potentially involve connections to a bunch of other switches, once
>> volume dictated I needed direct connections... and they don't want to
>> deal with that?
>>
>> Are there third parties that don't have vastly different terms for
>> local tandem services?
>>
>> Also, is it likely that I just don't understand what's going on? I
>> went circles with the sales rep to make sure I understood what he was
>> saying, but I could be wrong.
>>
>> -----
>> 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. 9, 2019
Connecting to Remote Tandems
by marylou@backuptelecom.com
There are a couple differences for various reasons. In the LERG there
are actually 3 tandems listed: One for Local, One for IntraLATA, and one
for FGD traffic. When you interconnect with only the ILEC, they only
have you establish 2 trunk groups. A local tandem trunk group that
handles the Local and IntraLATA traffic, and an Access Tandem trunk
group that handles the transit traffic you and the IXC carriers. When
you are connected to the ILEC, all 3 tandem offices in the LERG are
listed as the ILECs tandems.
If you hire a third party tandem provider for just "access traffic",
you're only changing that FGD tandem so the only trunk group you are
eliminating with the ILEC is the Access Tandem Trunk group.
If you're going to have a third party tandem provider handle your local
and IntraLATA traffic as well as your FGD traffic, then the LERG records
change significantly. Instead of using your own switch CLLI, you get a
POI CLLI for the LATA and populate the third party tandem provider's
switch CLLI in the actual switch field of the LERG. This tells everyone
that the NXXs belong to your company, but you're leasing another
company's switch to handle all the routing. This service eliminates the
need for all dedicated trunks between you and the ILEC so you just have
trunks between you and the third party tandem.
However, there is one more caveat and that is that it depends on what
ILEC you are interconnecting with. Verizon will allow the 3rd party
tandem provider to add your company's NXXs onto their existing trunk
group. CenturyLink and AT&T do not do that. They require the third party
tandem providers to install a dedicated trunk group for each company
that they are providing switching service for. Because a dedicated trunk
group between them and the ILEC costs them more, they will bill you
differently in those areas.
So the upside to having a third party tandem provider for Local
IntraLATA traffic is that you don't have to manage the Local IntraLATA
trunks yourself. The downside is that you probably will pay more per
minute if you send the traffic through the third party tandem provider.
Make sense?
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2019-08-09 02:42 PM, Mike Hammett wrote:
> I'm evaluating methods of extending our footprint. I purposely left
> out company names.
>
> One of the companies we talked to was really only interested in
> getting us the inbound long distance calls, not the local ones. Well,
> they would, but the terms were vastly different.
>
> Given that I still need to build out to connect to the local tandem,
> what's the point in using a third party to connect to long distance?
>
> Are the terms for connecting to the local tandems different because
> the access tandem is simpler, whereas the local tandem could
> potentially involve connections to a bunch of other switches, once
> volume dictated I needed direct connections... and they don't want to
> deal with that?
>
> Are there third parties that don't have vastly different terms for
> local tandem services?
>
> Also, is it likely that I just don't understand what's going on? I
> went circles with the sales rep to make sure I understood what he was
> saying, but I could be wrong.
>
> -----
> 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. 9, 2019
Connecting to Remote Tandems
by paul@timmins.net
I'm sure I know which one you're talking about. It's because they exist
in entirely different regulatory domains. The upside of inbound feature
group D is that you get to cut out a terrible ILEC tandem, and at least
the vendor I'm thinking of doesn't charge for the trunks themselves, so
you're at a very strong cost advantage on it.
Inbound local trunking, usually interconnection agreements dictate that
the trunks have to be dedicated per carrier, so you're just avoiding
sinking hardware cost and transport, but it still uses up considerable
resources at least in AT&T areas. So if you need 3 trunks to CHCGILWB's
tandem, they can't just route that to their trunks where they have
existing capacity, like FGD, but they have to install 3 shiny new T1s
just for your traffic, that they order as you, to their equipment. It's
stupid, convoluted, and wasteful but it's not the vendor's fault, it's
AT&T maintaining artificial barriers to competition. As if they'd have
it any other way.
-Paul
On 8/9/19 3:42 PM, Mike Hammett wrote:
> I'm evaluating methods of extending our footprint. I purposely left
> out company names.
>
> One of the companies we talked to was really only interested in
> getting us the inbound long distance calls, not the local ones. Well,
> they would, but the terms were vastly different.
>
> Given that I still need to build out to connect to the local tandem,
> what's the point in using a third party to connect to long distance?
>
> Are the terms for connecting to the local tandems different because
> the access tandem is simpler, whereas the local tandem could
> potentially involve connections to a bunch of other switches, once
> volume dictated I needed direct connections... ?and they don't want to
> deal with that?
>
> Are there third parties that don't have vastly different terms for
> local tandem services?
>
> Also, is it likely that I just don't understand what's going on? I
> went circles with the sales rep to make sure I understood what he was
> saying, but I could be wrong.
>
>
>
> -----
> 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. 9, 2019
Connecting to Remote Tandems
by voiceops@ics-il.net
I'm evaluating methods of extending our footprint. I purposely left out company names.
One of the companies we talked to was really only interested in getting us the inbound long distance calls, not the local ones. Well, they would, but the terms were vastly different.
Given that I still need to build out to connect to the local tandem, what's the point in using a third party to connect to long distance?
Are the terms for connecting to the local tandems different because the access tandem is simpler, whereas the local tandem could potentially involve connections to a bunch of other switches, once volume dictated I needed direct connections... and they don't want to deal with that?
Are there third parties that don't have vastly different terms for local tandem services?
Also, is it likely that I just don't understand what's going on? I went circles with the sales rep to make sure I understood what he was saying, but I could be wrong.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
Aug. 9, 2019