[VoiceOps] Connecting to Remote Tandems

Mary Lou Carey marylou at backuptelecom.com
Fri Jul 9 14:58:19 EDT 2021


I'm sure a lot of it has to do with more than is visible to us. I will 
message you privately so we can discuss options further.

MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111

On 2021-07-09 08:19 AM, Mike Hammett wrote:
> *nods*
> 
> I have been talking to people at Inteliquent and Peerless about their
> PSTN Connect services. My recent conversations reflect your
> observations.
> 
> 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.
> 
> 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?
> 
> 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.
> 
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
> 
> Midwest Internet Exchange
> http://www.midwest-ix.com
> 
> -------------------------
> 
> From: "Mary Lou Carey" <marylou at backuptelecom.com>
> To: "Mike Hammett" <voiceops at ics-il.net>
> Cc: "VoiceOps" <voiceops at voiceops.org>
> Sent: Thursday, July 8, 2021 2:12:04 PM
> Subject: Re: [VoiceOps] Connecting to Remote Tandems
> 
> The service you are looking for is called PSTN Connection service, but
> 
> you need to have either an FCC IPES certification (Direct Access to
> Numbering Resources) or a CLEC license. I have contacts at
> Inteliquent,
> Peerless, and Wide Voice if you need them. PSTN connection service is
> turned up on a per LATA basis so you don't have to limit yourself to
> one
> carrier for the entire country unless you want to. Its my
> understanding
> Wide Voice covers more areas for IPES providers than they do for CLEC.
> 
> Peerless and Wide Voice will work with anyone.....Inteliquent used to
> be
> willing to work with anyone but in the last year they've been less
> interested in serving IPES companies that don't have a significant
> amount of traffic to start out with. That could have changed since
> they
> were just bought out, but that's been my experience while helping
> carriers turn up their networks over the last year.
> 
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
> 
> On 2021-07-07 08:12 AM, Mike Hammett wrote:
>> At the suggestion of this mailing list, I started pursuing the
>> IVP/IPES route instead of trying to do my expansions via CLEC
>> authority.
>> 
>> I've had conversations with a few companies to enable the IPES
>> services, Verizon, Inteliquent, Intrado (West), and Peerless. I
>> haven't talked to Wide Voice because their stated coverage is
>> inadequate. I haven't talked to Level 3 because they never answered
>> me.
>> 
>>         * One of the conversations went nowhere because while they
> knew what
>> I was talking about, they didn't think they had a product for that.
>> Their rates for adjacent services were actually reasonable.
>>         * One had it productized, but had a 5 figure minimum monthly
> commit.
>> The stated reason was that the LECs are a pain and they wanted to
> make
>> sure they had a decent return before they committed resources.
>>         * One had only part of the solution, still requiring me to
> build out
>> the tandems myself for the ILEC interconnection.
>>         * One had it productized and had no monthly minimum.
>> 
>> Okay, so four very different responses from four companies. The one
>> seems like the a slam dunk, but being a slam drunk in the face of
> such
>> difficulty, I become skeptical. We're coming from a TDM, voice CLEC
>> background, not a retail SIP provider background. Is there something
>> I'm underestimating in this process?
>> 
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>> 
>> Midwest Internet Exchange
>> http://www.midwest-ix.com
>> 
>> -------------------------
>> 
>> From: "Mike Hammett" <voiceops at ics-il.net>
>> To: "VoiceOps" <voiceops at voiceops.org>
>> Sent: Friday, August 9, 2019 2:42:37 PM
>> Subject: [VoiceOps] Connecting to Remote Tandems
>> 
>> 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


More information about the VoiceOps mailing list