Vonage was originally formed as the Minutes Exchange for voip peering. We then spun part of the free world dialup into iPeerX around 2005; sold it to Eli Katz a few years later.
The key problems at the time were: 1. there were too few ITSP numbers to make the effort worthwhile; The exception was the cable companies which I believe had their own peering through cable labs. 2. There was fear that publishing voip addresses would lead to hacking and spam calls. /Ed PS. If anyone wants tickets to VON Builder next week, drop me an email. ([email protected]) From: VoiceOps <[email protected]> on behalf of Pinchas Neiman via VoiceOps <[email protected]> Date: Tuesday, October 24, 2023 at 10:45 AM To: chris <[email protected]> Cc: voiceops <[email protected]> Subject: Re: [VoiceOps] Voice Peering Maybe the signup fee, and lookup time is what killed the idea? If that's the case, we could solve it by downloading the list preemptively, for the signup we could use some cheap hosting, and instead verifying it with crypto. We could possibly cryptographically verify it by showing a STIR/SHAKEN passport that was signed by one of the major brands. All the owner needs is to call his number from a landline, capture the SIP invite and submit it to the website. On Tue, Oct 24, 2023 at 10:36 AM chris <[email protected]<mailto:[email protected]>> wrote: +1 enum was great stuff Here in NYC early 2000s we had Stealth doing the VPF (voice peering fabric) https://www.channelfutures.com/telephony-uc-collaboration/xo-joins-stealths-vpf Chris On Tue, Oct 24, 2023, 10:32 AM Michael Graves via VoiceOps <[email protected]<mailto:[email protected]>> wrote: Every time this comes up I am reminded of ENUM, ITAD, Freenum.org and John Todd, long ago once of the brilliant people at Digium. More recently at Quad9. Is Carrier ENUM still a thing? Michael Graves [email protected]<mailto:[email protected]> o: (713) 861-4005 c: (713) 201-1262 sip:[email protected] From: VoiceOps <[email protected]<mailto:[email protected]>> On Behalf Of Mike Hammett via VoiceOps Sent: Tuesday, October 24, 2023 9:29 AM To: Pinchas Neiman <[email protected]<mailto:[email protected]>> Cc: VoiceOps <[email protected]<mailto:[email protected]>> Subject: Re: [VoiceOps] Voice Peering https://wirevolution.com/step-8-register-your-phone-number-at-e164org/ Most of the links have died, so that idea has likely also sunset. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ________________________________ From: "Pinchas Neiman via VoiceOps" <[email protected]<mailto:[email protected]>> To: "Alex Balashov" <[email protected]<mailto:[email protected]>> Cc: "VoiceOps" <[email protected]<mailto:[email protected]>> Sent: Tuesday, October 24, 2023 9:05:26 AM Subject: Re: [VoiceOps] Voice Peering I am also quitely new in the industry, wondered a while about this possibility, and never realized that Neutral Tandem/Inteliquent are exactly this. I wonder about a hybrid idea, instead of using a global bridge, we would use direct end peer to end peer SIP, the list of DID->IP translation will be maintained on a public website, any DID could be added to that website by requesting a call to that DID@IP using the website, there may be a nominal listing fee, in order to maintain the website. Once in a while an automated script could download the config from the website and update local routing rules. Were this idea or alike ever implemented? legal issues? On Tue, Oct 24, 2023 at 9:25 AM Alex Balashov via VoiceOps <[email protected]<mailto:[email protected]>> wrote: I think the realistic responses are going to be some combination of: 1) "Congratulations, you just invented Neutral Tandem/Inteliquent/whatever they are this week" 2) "The SIP peering exchange has been proclaimed every year since the early 2000s" 3) "This is quietly happening for years now anyway, just not in the way you've got in mind." -- Alex > On 24 Oct 2023, at 08:49, Mike Hammett via VoiceOps > <[email protected]<mailto:[email protected]>> wrote: > > This was in another thread, but I broke it out into it's own conversation. > Someone had asked: > > --- > Hi, > > I am joining this thread late, but, would anyone out there be interested in > exchanging traffic with other carriers directly over SIP? > > The service would just look like a carrier, except it would know how to reach > all other participants directly with SIP, bypassing TDM land, and enabling > rich media as a fringe benefit, as media would be direct between endpoints. > > I have a proof of concept and am wondering who out there might be willing to > do some testing. > > Email me directly if interested, to talk about your network and how something > like this might fit in. > > Cheers, > > Jawaid > --- > > > https://www.voip-info.org/the-voice-peering-fabric/ > I can't find anything on this in 15 years, so I'm guessing it didn't work out > for one reason or another. Can anyone impart some history there? > > > > ----- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > > > Midwest Internet Exchange > http://www.midwest-ix.com > > > > _______________________________________________ > VoiceOps mailing list > [email protected]<mailto:[email protected]> > https://puck.nether.net/mailman/listinfo/voiceops -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800 _______________________________________________ VoiceOps mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops -- Pinchas S. Neiman Software Engineer At ESEQ Technology Corp. 845.213.1229 #2 [Image removed by sender.] _______________________________________________ VoiceOps mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops -- Pinchas S. Neiman Software Engineer At ESEQ Technology Corp. 845.213.1229 #2 [Image removed by sender.]
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
