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" <voice...@ics-il.net>
To: "VoiceOps" <voiceops@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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to