<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* I suspect we'll be keeping our own SS7 for a while. We're already in the CO for other reasons and there are more points of failure than a circuit from one room to the other. As you alluded to, if I'm already there, it's hard for them to do it any cheaper than I am.<br><br><br><br>*sigh* The world of telecom... ;-)<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:16:22 PM<br><b>Subject: </b>Re: [VoiceOps] Connecting to Remote Tandems<br><br>I forgot to mention one more thing......if the third party tandem <br>provider is handling the local and intraLATA traffic for you as well as <br>the FGD traffic, then you don't have to mess with managing your own SS7 <br>network or programming your switch for the PSTN routing.<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 03:14 PM, Mary Lou Carey wrote:<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<br>> one for FGD traffic. When you interconnect with only the ILEC, they<br>> only have you establish 2 trunk groups. A local tandem trunk group<br>> that handles the Local and IntraLATA traffic, and an Access Tandem<br>> trunk group that handles the transit traffic you and the IXC carriers.<br>> When you are connected to the ILEC, all 3 tandem offices in the LERG<br>> are 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<br>> local and IntraLATA traffic as well as your FGD traffic, then the LERG<br>> records change significantly. Instead of using your own switch CLLI,<br>> you get a POI CLLI for the LATA and populate the third party tandem<br>> provider's switch CLLI in the actual switch field of the LERG. This<br>> tells everyone that the NXXs belong to your company, but you're<br>> leasing another company's switch to handle all the routing. This<br>> service eliminates the need for all dedicated trunks between you and<br>> the ILEC so you just have trunks between you and the third party<br>> 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<br>> party tandem providers to install a dedicated trunk group for each<br>> company that they are providing switching service for. Because a<br>> dedicated trunk group between them and the ILEC costs them more, they<br>> will bill you 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<br>> provider. 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></body></html>