<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'>That's the first I've heard of Wide Voice. Their network looks little sparse at the moment. I wonder if it's on-demand, as in once you inquire about a LATA, they build it out.<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>Monday, February 8, 2021 5:33:19 PM<br><b>Subject: </b>Re: [VoiceOps] Connecting to Remote Tandems<br><br>You can get a PSTN Connection Service from Peerless or Wide Voice. <br>Inteliquent used to offer that service but they have backed away from it <br>recently.<br><br>To make it simple, you have to get certified as an Interconnected VOIP <br>carrier and then set up SIP trunks with your PSTN Connection provider. <br>You order a POI CLLI and LRN NXX for every LATA that you want to enter <br>and point your traffic to the PSTN Connection provider's switch in the <br>LERG. You still have all your own NXXs and LRNs, but you can get rid of <br>your SS7 network because the PSTN Connection Service Provider handles <br>that piece. You still do all your own porting and maintain all your <br>connections with 911, LD, VOIP providers. If you want more information <br>on how it all works, just message me privately.<br><br>MARY LOU CAREY<br>BackUP Telecom Consulting<br>Office: 615-791-9969<br>Cell: 615-796-1111<br><br>On 2021-02-08 03:35 PM, Mike Hammett wrote:<br>> Due to receiving several offlist e-mails about this point, I wanted to<br>> point out that I'm not looking to do SIP directly to an ILEC tandem. I<br>> assume there would be some abstraction layer happening by a third<br>> party.<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>> -------------------------<br>> <br>> From: "Mike Hammett" <voiceops@ics-il.net><br>> To: "VoiceOps" <voiceops@voiceops.org><br>> Sent: Monday, February 8, 2021 9:24:57 AM<br>> Subject: Re: [VoiceOps] Connecting to Remote Tandems<br>> <br>> I did want to circle back on this.<br>> <br>> I am currently a CLEC with traditional voice services in a single LATA<br>> on a single set of tandems. We have SS7, do our own porting, etc.<br>> I understand that going interconnected VoIP (instead of CLEC) may be<br>> easier for my expansions.<br>> <br>> So that I don't have to drag T1s all over the place, what options do I<br>> have in front of me? To be clear, I am looking for specific providers<br>> and products, even off-list solicitations.<br>> <br>> I'm not afraid of T1s, they're just expensive. I got a quote for a<br>> single T1 to the facility where the other tandem in our LATA is, and<br>> it was far more expensive than just sending the calls out our<br>> termination providers. If I need more than one T1 (one for each<br>> tandem), then I'm really priced out of the market. Obviously that<br>> course of action wouldn't help me for my own number blocks.<br>> <br>> I looked at straight DID\minute services, but as some of our past (and<br>> potential future) customers have several hundreds of DIDs compared to<br>> the amount of traffic they'd have, that gets a difficult to operate<br>> in.<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>> -------------------------<br>> <br>> From: "Mike Hammett" <voiceops@ics-il.net><br>> To: "VoiceOps" <voiceops@voiceops.org><br>> Sent: Friday, August 9, 2019 2:42:37 PM<br>> Subject: [VoiceOps] Connecting to Remote Tandems<br>> <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>> _______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br>> <br>> _______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br>> _______________________________________________<br>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br></div><br></div></body></html>