Wide Voice used to run the PSTN connectivity (they may still do it, I haven't investigated) for FreeConferenceCall.com and other similar services. They probably had to change up the business model when intercarrier compensation rates dried up.
On Mon, Feb 8, 2021 at 3:55 PM Mike Hammett <voice...@ics-il.net> wrote: > 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. > > > > ----- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > > > Midwest Internet Exchange > http://www.midwest-ix.com > > > > ------------------------------ > *From: *"Mary Lou Carey" <mary...@backuptelecom.com> > *To: *"Mike Hammett" <voice...@ics-il.net> > *Cc: *"VoiceOps" <voiceops@voiceops.org> > *Sent: *Monday, February 8, 2021 5:33:19 PM > *Subject: *Re: [VoiceOps] Connecting to Remote Tandems > > You can get a PSTN Connection Service from Peerless or Wide Voice. > Inteliquent used to offer that service but they have backed away from it > recently. > > To make it simple, you have to get certified as an Interconnected VOIP > carrier and then set up SIP trunks with your PSTN Connection provider. > You order a POI CLLI and LRN NXX for every LATA that you want to enter > and point your traffic to the PSTN Connection provider's switch in the > LERG. You still have all your own NXXs and LRNs, but you can get rid of > your SS7 network because the PSTN Connection Service Provider handles > that piece. You still do all your own porting and maintain all your > connections with 911, LD, VOIP providers. If you want more information > on how it all works, just message me privately. > > MARY LOU CAREY > BackUP Telecom Consulting > Office: 615-791-9969 > Cell: 615-796-1111 > > On 2021-02-08 03:35 PM, Mike Hammett wrote: > > Due to receiving several offlist e-mails about this point, I wanted to > > point out that I'm not looking to do SIP directly to an ILEC tandem. I > > assume there would be some abstraction layer happening by a third > > party. > > > > ----- > > 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: Monday, February 8, 2021 9:24:57 AM > > Subject: Re: [VoiceOps] Connecting to Remote Tandems > > > > I did want to circle back on this. > > > > I am currently a CLEC with traditional voice services in a single LATA > > on a single set of tandems. We have SS7, do our own porting, etc. > > I understand that going interconnected VoIP (instead of CLEC) may be > > easier for my expansions. > > > > So that I don't have to drag T1s all over the place, what options do I > > have in front of me? To be clear, I am looking for specific providers > > and products, even off-list solicitations. > > > > I'm not afraid of T1s, they're just expensive. I got a quote for a > > single T1 to the facility where the other tandem in our LATA is, and > > it was far more expensive than just sending the calls out our > > termination providers. If I need more than one T1 (one for each > > tandem), then I'm really priced out of the market. Obviously that > > course of action wouldn't help me for my own number blocks. > > > > I looked at straight DID\minute services, but as some of our past (and > > potential future) customers have several hundreds of DIDs compared to > > the amount of traffic they'd have, that gets a difficult to operate > > in. > > > > ----- > > 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 > > _______________________________________________ > 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
