<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*<div><br></div><div>I have been talking to people at Inteliquent and Peerless about their PSTN Connect services. My recent conversations reflect your observations.</div><div><br></div><div>I didn't bother with Wide Voice because their coverage seemed to be minuscule (didn't even have coverage in Chicago). If you think their website's stated coverage isn't accurate, I'd appreciate an introduction.</div><div><br></div><div><br></div><div>Do you think the vast difference in approaches (and thus requirements) taken by Inteliquent vs. Peerless or Wide Voice are simply business interest vs. something fundamental that I'm missing?</div><div><br></div><div><br></div><div><br></div><div>I'm trying to be somewhat vague in my statements and questions, erring on the side of caution regarding whatever NDAs I may have signed and speaking in a public venue.<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>Thursday, July 8, 2021 2:12:04 PM<br><b>Subject: </b>Re: [VoiceOps] Connecting to Remote Tandems<br><br>The service you are looking for is called PSTN Connection service, but <br>you need to have either an FCC IPES certification (Direct Access to <br>Numbering Resources) or a CLEC license. I have contacts at Inteliquent, <br>Peerless, and Wide Voice if you need them. PSTN connection service is <br>turned up on a per LATA basis so you don't have to limit yourself to one <br>carrier for the entire country unless you want to. Its my understanding <br>Wide Voice covers more areas for IPES providers than they do for CLEC.<br><br>Peerless and Wide Voice will work with anyone.....Inteliquent used to be <br>willing to work with anyone but in the last year they've been less <br>interested in serving IPES companies that don't have a significant <br>amount of traffic to start out with. That could have changed since they <br>were just bought out, but that's been my experience while helping <br>carriers turn up their networks over the last year.<br><br>MARY LOU CAREY<br>BackUP Telecom Consulting<br>Office: 615-791-9969<br>Cell: 615-796-1111<br><br>On 2021-07-07 08:12 AM, Mike Hammett wrote:<br>> At the suggestion of this mailing list, I started pursuing the<br>> IVP/IPES route instead of trying to do my expansions via CLEC<br>> authority.<br>> <br>> I've had conversations with a few companies to enable the IPES<br>> services, Verizon, Inteliquent, Intrado (West), and Peerless. I<br>> haven't talked to Wide Voice because their stated coverage is<br>> inadequate. I haven't talked to Level 3 because they never answered<br>> me.<br>> <br>> * One of the conversations went nowhere because while they knew what<br>> I was talking about, they didn't think they had a product for that.<br>> Their rates for adjacent services were actually reasonable.<br>> * One had it productized, but had a 5 figure minimum monthly commit.<br>> The stated reason was that the LECs are a pain and they wanted to make<br>> sure they had a decent return before they committed resources.<br>> * One had only part of the solution, still requiring me to build out<br>> the tandems myself for the ILEC interconnection.<br>> * One had it productized and had no monthly minimum.<br>> <br>> Okay, so four very different responses from four companies. The one<br>> seems like the a slam dunk, but being a slam drunk in the face of such<br>> difficulty, I become skeptical. We're coming from a TDM, voice CLEC<br>> background, not a retail SIP provider background. Is there something<br>> I'm underestimating in this process?<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>> VoiceOps mailing list<br>> VoiceOps@voiceops.org<br>> https://puck.nether.net/mailman/listinfo/voiceops<br></div><br></div></div></body></html>