<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>*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.<div><br></div><div><br><div>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.</div><div><br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br><br><br>Midwest Internet Exchange<br>http://www.midwest-ix.com<br><br><span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Mary Lou Carey" <marylou@backuptelecom.com><br><b>To: </b>"Mike Hammett" <voiceops@ics-il.net><br><b>Cc: </b>"VoiceOps" <voiceops@voiceops.org><br><b>Sent: </b>Friday, August 9, 2019 3:14:38 PM<br><b>Subject: </b>Re: [VoiceOps] Connecting to Remote Tandems<br><br>There are a couple differences for various reasons. In the LERG there <br>are actually 3 tandems listed: One for Local, One for IntraLATA, and one <br>for FGD traffic. When you interconnect with only the ILEC, they only <br>have you establish 2 trunk groups. A local tandem trunk group that <br>handles the Local and IntraLATA traffic, and an Access Tandem trunk <br>group that handles the transit traffic you and the IXC carriers. When <br>you are connected to the ILEC, all 3 tandem offices in the LERG are <br>listed as the ILECs tandems.<br><br>If you hire a third party tandem provider for just "access traffic", <br>you're only changing that FGD tandem so the only trunk group you are <br>eliminating with the ILEC is the Access Tandem Trunk group.<br><br>If you're going to have a third party tandem provider handle your local <br>and IntraLATA traffic as well as your FGD traffic, then the LERG records <br>change significantly. Instead of using your own switch CLLI, you get a <br>POI CLLI for the LATA and populate the third party tandem provider's <br>switch CLLI in the actual switch field of the LERG. This tells everyone <br>that the NXXs belong to your company, but you're leasing another <br>company's switch to handle all the routing. This service eliminates the <br>need for all dedicated trunks between you and the ILEC so you just have <br>trunks between you and the third party tandem.<br><br>However, there is one more caveat and that is that it depends on what <br>ILEC you are interconnecting with. Verizon will allow the 3rd party <br>tandem provider to add your company's NXXs onto their existing trunk <br>group. CenturyLink and AT&T do not do that. They require the third party <br>tandem providers to install a dedicated trunk group for each company <br>that they are providing switching service for. Because a dedicated trunk <br>group between them and the ILEC costs them more, they will bill you <br>differently in those areas.<br><br>So the upside to having a third party tandem provider for Local <br>IntraLATA traffic is that you don't have to manage the Local IntraLATA <br>trunks yourself. The downside is that you probably will pay more per <br>minute if you send the traffic through the third party tandem provider. <br>Make sense?<br><br><br>MARY LOU CAREY<br>BackUP Telecom Consulting<br>Office: 615-791-9969<br>Cell: 615-796-1111<br><br>On 2019-08-09 02:42 PM, Mike Hammett wrote:<br>> I'm evaluating methods of extending our footprint. I purposely left<br>> out company names.<br>> <br>> One of the companies we talked to was really only interested in<br>> getting us the inbound long distance calls, not the local ones. Well,<br>> they would, but the terms were vastly different.<br>> <br>> Given that I still need to build out to connect to the local tandem,<br>> what's the point in using a third party to connect to long distance?<br>> <br>> Are the terms for connecting to the local tandems different because<br>> the access tandem is simpler, whereas the local tandem could<br>> potentially involve connections to a bunch of other switches, once<br>> volume dictated I needed direct connections... and they don't want to<br>> deal with that?<br>> <br>> Are there third parties that don't have vastly different terms for<br>> local tandem services?<br>> <br>> Also, is it likely that I just don't understand what's going on? I<br>> went circles with the sales rep to make sure I understood what he was<br>> saying, but I could be wrong.<br>> <br>> -----<br>> Mike Hammett<br>> Intelligent Computing Solutions<br>> http://www.ics-il.com<br>> <br>> Midwest Internet Exchange<br>> http://www.midwest-ix.com<br>> _______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br></div><br></div></div></div></body></html>