<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jared,</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">This is what you were talking about I believe,
</span><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><a href="https://enumer.org/" id="OWAf09b6eae-bbca-5d8f-5c9f-3f9ed3d140bf" class="OWAAutoLink">https://enumer.org/</a> (2017 article on it
<a href="https://medium.com/@emer.tech/voip-made-free-with-blockchain-introducing-enumer-35235c4abec5" id="LPNoLPOWALinkPreview">
https://medium.com/@emer.tech/voip-made-free-with-blockchain-introducing-enumer-35235c4abec5</a>)</span><span style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">. I don't know much about the project and am not supporting
it, just providing the information.</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Brian</div>
<div id="appendonsend"></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div id="divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> VoiceOps <voiceops-bounces@voiceops.org> on behalf of Alex Balashov via VoiceOps <voiceops@voiceops.org><br>
<b>Sent:</b> Tuesday, October 24, 2023 12:07 PM<br>
<b>To:</b> VoiceOps <voiceops@voiceops.org><br>
<b>Subject:</b> Re: [VoiceOps] Voice Peering</span>
<div> </div>
</div>
<div><span style="font-size: 11pt;">I think that, as has always been the case with these ideas, fascinating technical intricacies miss the forest for the trees; the economics just don't bear out. The time to try this was in the 2000s. Boat's gone.<br>
<br>
By this point, there has been an enormous amount of industry consolidation. A very small oligopoly of well-known CLECs feeds the VoIP industry, and they already have SIP interconnects to each other, and have had them since the Jurassic era or the Cambrian explosion
or whatever.<br>
<br>
We all sit in tiny creeks massively downstream of these entities, and would save vanishingly little peering with each other (and less and less with time, given the trend of wholesale LD termination, at least in the US).<br>
<br>
-- Alex<br>
<br>
> On 24 Oct 2023, at 14:59, Jared Geiger via VoiceOps <voiceops@voiceops.org> wrote:<br>
><br>
> There was a project, ENUMER, to put DIDs in a blockchain and an ENUM server lookup frontend to it to facilitate peering. I didn't saw many entries in the database back when it launched. I haven't looked in a while and don't remember which blockchain it was
on.<br>
><br>
> I believe TNS and Neustar operate a private ENUM peering service. XConnect used to but I didn't see it on their webpage when I looked today.<br>
><br>
> I vaguely recall hearing that Mavenir offered a service for cellular providers to exchange HD Voice traffic between each other in the US. Like the Cable Labs ENUM peering service, I think its a private club offering only.<br>
><br>
> On the Toll Free side, Teliax offers tollfree.exchange which allows RESPORGs to join directly, hand off calls between each other, and set rates.<br>
><br>
><br>
><br>
> On Tue, Oct 24, 2023 at 8:12 AM Ed Guy via VoiceOps <voiceops@voiceops.org> wrote:<br>
> Vonage was originally formed as the Minutes Exchange for voip peering.<br>
> We then spun part of the free world dialup into iPeerX around 2005; sold it to Eli Katz a few years later.<br>
> The key problems at the time were:<br>
> • 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.<br>
> • There was fear that publishing voip addresses would lead to hacking and spam calls.<br>
> /Ed<br>
> PS. If anyone wants tickets to VON Builder next week, drop me an email. (edguy@eguy.org)<br>
> From: VoiceOps <voiceops-bounces@voiceops.org> on behalf of Pinchas Neiman via VoiceOps <voiceops@voiceops.org><br>
> Date: Tuesday, October 24, 2023 at 10:45 AM<br>
> To: chris <tknchris@gmail.com><br>
> Cc: voiceops <voiceops@voiceops.org><br>
> Subject: Re: [VoiceOps] Voice Peering<br>
> Maybe the signup fee, and lookup time is what killed the idea?<br>
> 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.<br>
> We could possibly cryptographically verify it by showing a STIR/SHAKEN passport that was signed by one of the major brands.<br>
> All the owner needs is to call his number from a landline, capture the SIP invite and submit it to the website.<br>
> On Tue, Oct 24, 2023 at 10:36 AM chris <tknchris@gmail.com> wrote:<br>
> +1 enum was great stuff<br>
> Here in NYC early 2000s we had Stealth doing the VPF (voice peering fabric)<br>
> <a href="https://www.channelfutures.com/telephony-uc-collaboration/xo-joins-stealths-vpf" id="OWA59446720-d83b-c073-9a42-9b36137465c6" class="OWAAutoLink" data-auth="NotApplicable">
https://www.channelfutures.com/telephony-uc-collaboration/xo-joins-stealths-vpf</a><br>
> Chris<br>
> On Tue, Oct 24, 2023, 10:32 AM Michael Graves via VoiceOps <voiceops@voiceops.org> wrote:<br>
> 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.<br>
> Is Carrier ENUM still a thing?<br>
> Michael Graves<br>
> mgraves@mstvp.com<br>
> o: (713) 861-4005<br>
> c: (713) 201-1262<br>
> sip:mgraves@mjg.onsip.com<br>
> From: VoiceOps <voiceops-bounces@voiceops.org> On Behalf Of Mike Hammett via VoiceOps<br>
> Sent: Tuesday, October 24, 2023 9:29 AM<br>
> To: Pinchas Neiman <neimanpinchas@gmail.com><br>
> Cc: VoiceOps <voiceops@voiceops.org><br>
> Subject: Re: [VoiceOps] Voice Peering<br>
> <a href="https://wirevolution.com/step-8-register-your-phone-number-at-e164org/" id="OWA496ecb83-aeb1-3bad-d702-b0944b408a7c" class="OWAAutoLink" data-auth="NotApplicable">
https://wirevolution.com/step-8-register-your-phone-number-at-e164org/</a><br>
> Most of the links have died, so that idea has likely also sunset.<br>
><br>
><br>
> -----<br>
> Mike Hammett<br>
> Intelligent Computing Solutions<br>
> <a href="http://www.ics-il.com" id="OWAbaee4ad2-3495-a4ed-84ff-44daaacd9252" class="OWAAutoLink" data-auth="NotApplicable">
http://www.ics-il.com</a><br>
><br>
><br>
><br>
> Midwest Internet Exchange<br>
> <a href="http://www.midwest-ix.com" id="OWA2944c339-bb64-541f-f24e-5b0fe3b22eb4" class="OWAAutoLink" data-auth="NotApplicable">
http://www.midwest-ix.com</a><br>
><br>
> From: "Pinchas Neiman via VoiceOps" <voiceops@voiceops.org><br>
> To: "Alex Balashov" <abalashov@evaristesys.com><br>
> Cc: "VoiceOps" <voiceops@voiceops.org><br>
> Sent: Tuesday, October 24, 2023 9:05:26 AM<br>
> Subject: Re: [VoiceOps] Voice Peering<br>
> I am also quitely new in the industry, wondered a while about this possibility, and never realized that Neutral Tandem/Inteliquent are exactly this.<br>
> 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.<br>
> Once in a while an automated script could download the config from the website and update local routing rules.<br>
> Were this idea or alike ever implemented? legal issues?<br>
> On Tue, Oct 24, 2023 at 9:25 AM Alex Balashov via VoiceOps <voiceops@voiceops.org> wrote:<br>
> I think the realistic responses are going to be some combination of:<br>
><br>
> 1) "Congratulations, you just invented Neutral Tandem/Inteliquent/whatever they are this week"<br>
><br>
> 2) "The SIP peering exchange has been proclaimed every year since the early 2000s"<br>
><br>
> 3) "This is quietly happening for years now anyway, just not in the way you've got in mind."<br>
><br>
> -- Alex<br>
><br>
> > On 24 Oct 2023, at 08:49, Mike Hammett via VoiceOps <voiceops@voiceops.org> wrote:<br>
> ><br>
> > This was in another thread, but I broke it out into it's own conversation. Someone had asked:<br>
> ><br>
> > ---<br>
> > Hi,<br>
> ><br>
> > I am joining this thread late, but, would anyone out there be interested in exchanging traffic with other carriers directly over SIP?<br>
> ><br>
> > 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.<br>
> ><br>
> > I have a proof of concept and am wondering who out there might be willing to do some testing.<br>
> ><br>
> > Email me directly if interested, to talk about your network and how something like this might fit in.<br>
> ><br>
> > Cheers,<br>
> ><br>
> > Jawaid<br>
> > ---<br>
> ><br>
> ><br>
> > <a href="https://www.voip-info.org/the-voice-peering-fabric/" id="OWA2c2a62a6-12aa-f9e5-8ff2-1c91b3baa7f0" class="OWAAutoLink" data-auth="NotApplicable">
https://www.voip-info.org/the-voice-peering-fabric/</a><br>
> > 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?<br>
> ><br>
> ><br>
> ><br>
> > -----<br>
> > Mike Hammett<br>
> > Intelligent Computing Solutions<br>
> > <a href="http://www.ics-il.com" id="OWAc8c99204-ea2e-5e5a-4764-57e3d5f9a269" class="OWAAutoLink" data-auth="NotApplicable">
http://www.ics-il.com</a><br>
> ><br>
> ><br>
> ><br>
> > Midwest Internet Exchange<br>
> > <a href="http://www.midwest-ix.com" id="OWAddd8ebbe-6a17-178d-7e31-996c41ff220b" class="OWAAutoLink" data-auth="NotApplicable">
http://www.midwest-ix.com</a><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > VoiceOps mailing list<br>
> > VoiceOps@voiceops.org<br>
> > <a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWAf37e7152-5256-6b7c-03a2-fcd103bdaa7e" class="OWAAutoLink" data-auth="NotApplicable">
https://puck.nether.net/mailman/listinfo/voiceops</a><br>
><br>
><br>
> --<br>
> Alex Balashov<br>
> Principal Consultant<br>
> Evariste Systems LLC<br>
> Web: <a href="https://evaristesys.com" id="OWAc89af3ce-e21f-d5e6-b725-dd85fc00c4fe" class="OWAAutoLink" data-auth="NotApplicable">
https://evaristesys.com</a><br>
> Tel: +1-706-510-6800<br>
><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> VoiceOps@voiceops.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWA2a5a80da-c3da-fb03-a067-8a1459c81b38" class="OWAAutoLink" data-auth="NotApplicable">
https://puck.nether.net/mailman/listinfo/voiceops</a><br>
><br>
> --<br>
> Pinchas S. Neiman<br>
> Software Engineer At ESEQ Technology Corp.<br>
> 845.213.1229 #2<br>
><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> VoiceOps@voiceops.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWA51ba1542-419a-8009-ae7b-5a3a98c758b5" class="OWAAutoLink" data-auth="NotApplicable">
https://puck.nether.net/mailman/listinfo/voiceops</a><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> VoiceOps@voiceops.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWA01b75e96-db3a-2a6a-a628-b9fd116f9e86" class="OWAAutoLink" data-auth="NotApplicable">
https://puck.nether.net/mailman/listinfo/voiceops</a><br>
><br>
> --<br>
> Pinchas S. Neiman<br>
> Software Engineer At ESEQ Technology Corp.<br>
> 845.213.1229 #2<br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> VoiceOps@voiceops.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWA78b4e428-47f7-dd3f-9216-99f92db62a01" class="OWAAutoLink" data-auth="NotApplicable">
https://puck.nether.net/mailman/listinfo/voiceops</a><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> VoiceOps@voiceops.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWA2691de70-d5b8-8dc5-47b2-1c31b89192f7" class="OWAAutoLink" data-auth="NotApplicable">
https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
--<br>
Alex Balashov<br>
Principal Consultant<br>
Evariste Systems LLC<br>
Web: <a href="https://evaristesys.com" id="OWA03cde8da-3730-4dce-2b35-c934d41f1703" class="OWAAutoLink" data-auth="NotApplicable">
https://evaristesys.com</a><br>
Tel: +1-706-510-6800<br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
VoiceOps@voiceops.org<br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" id="OWAfed59cac-5fd9-db60-2ec4-060f9824c6b6" class="OWAAutoLink" data-auth="NotApplicable">https://puck.nether.net/mailman/listinfo/voiceops</a></span></div>
</body>
</html>