Re: [VoiceOps] Voice Peering

On Wed, 25 Oct 2023, Mike Johnston via VoiceOps wrote: Anyways, say your system is getting a call from 555-555-1234. So you do a DNS query against...I do not know. dig TXT 4.3.2.1.5.5.5.5.5.5.i-do-not-know. How do you take an incoming call, from an IP you do not know, turn that IP and

Re: [VoiceOps] Voice Peering

d ‘$BAD_COMPANY’ and start rejecting their calls. The system > would settle our fairly quickly > > > > From: Peter Beckman > > Date: Wednesday, October 25, 2023 at 12:04 PM > > To: Matthew Crocker > > Cc: Pinchas Neiman , Jawaid Bazyar < > jaw...@bazyar.net

Re: [VoiceOps] Voice Peering

, October 25, 2023 at 5:08 PM To: Matthew Crocker Cc: Pinchas Neiman , Jawaid Bazyar , VoiceOps Subject: Re: [VoiceOps] Voice Peering CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe. This

Re: [VoiceOps] Voice Peering

in various AWS/Azure/GoogleCloud VPS From: Pinchas Neiman Date: Wednesday, October 25, 2023 at 11:18 AM To: Jawaid Bazyar Cc: Matthew Crocker , voiceops Subject: Re: [VoiceOps] Voice Peering CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless

Re: [VoiceOps] Voice Peering

> any business who also leases numbers INDIRECTLY gets cut out and still needs to pay their upstream carrier(s) to place/receive calls Yes, true...but I don't really care about retail consumers or resellers. If they are doing enough VoIP volume that they care about peering, they can go through the

Re: [VoiceOps] Voice Peering

> On 25 Oct 2023, at 15:12, Michael Graves wrote: > > The apparent elegance of a technology can be entrancing. > > To quote the great Leonard Cohen, "We're blinded by the beauty of our > weapons." Indeed. I think that sums up ENUM peering, e164.org , DUNDi federations, and

Re: [VoiceOps] Voice Peering

s On Behalf Of Alex Balashov via VoiceOps Sent: Wednesday, October 25, 2023 2:01 PM To: VoiceOps Subject: Re: [VoiceOps] Voice Peering > On 25 Oct 2023, at 11:18, Pinchas Neiman via VoiceOps > wrote: > > By reading the RFCs I was able to grasp 75% of it, it's well written &g

Re: [VoiceOps] Voice Peering

> On 24 Oct 2023, at 21:13, Peter Beckman via VoiceOps > wrote: > > The challenge is how do you authenticate the end "carrier" or service > provider? > > Sure, anyone who leases numbers directly from NANPA can look up the carrier > of record and exchange traffic directly, but any business who

Re: [VoiceOps] Voice Peering

> On 25 Oct 2023, at 11:18, Pinchas Neiman via VoiceOps > wrote: > > By reading the RFCs I was able to grasp 75% of it, it's well written and > covers your clear constraint, at least on how to verify the SIP header comes > from a trustworthy authority (If you agree on the root authority) > P

Re: [VoiceOps] Voice Peering

Who can source email from a domain is more-or-less a solved problem by using DNS SPF records. An SPF record is a list of IP addresses[1] that is allowed to send email for a domain. When an email server receives an email, best practice is to do a DNS lookup for the SPF of the alleged sender do

Re: [VoiceOps] Voice Peering

inchas Neiman via VoiceOps Sent: Wednesday, October 25, 2023 11:54 AM To: Matthew Crocker Cc: voiceops Subject: Re: [VoiceOps] Voice Peering And a pool of peers trusting themselves, could establish a mutual database where they could award or revoke trust to companies or CAs. Then other peers could

Re: [VoiceOps] Voice Peering

12:04 PM > *To: *Matthew Crocker > *Cc: *Pinchas Neiman , Jawaid Bazyar < > jaw...@bazyar.net>, voiceops > *Subject: *Re: [VoiceOps] Voice Peering > > CAUTION: This email originated from outside of Crocker. Do not click links > or open attachments unless you recogniz

Re: [VoiceOps] Voice Peering

Cc: Pinchas Neiman , Jawaid Bazyar , voiceops Subject: Re: [VoiceOps] Voice Peering CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe. STIR/SHAKEN does not delegate any authority to anyone

Re: [VoiceOps] Voice Peering

xport/upload (hacked BGP?) numbers they are willing to receive calls on to the peering proxy. Proxies can be spun up in various AWS/Azure/GoogleCloud VPS From: Pinchas Neiman Date: Wednesday, October 25, 2023 at 11:18 AM To: Jawaid Bazyar Cc: Matthew Crocker , voiceops Subject: Re: [VoiceOps] V

Re: [VoiceOps] Voice Peering

, voiceops Subject: Re: [VoiceOps] Voice Peering CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe. By reading the RFCs I was able to grasp 75% of it, it's well written and covers

Re: [VoiceOps] Voice Peering

By reading the RFCs I was able to grasp 75% of it, it's well written and covers your *clear *constraint, at least on how to verify the SIP header comes from a trustworthy authority (If you agree on the root authority) Practically implementing STIR/SHAKEN has bureaucracy involved. On Tue, Oct 24, 2

Re: [VoiceOps] Voice Peering

Is there a good clear document somewhere describing how STIR/SHAKEN is supposed to work? On Tue, Oct 24, 2023 at 9:33 PM Matthew Crocker via VoiceOps < voiceops@voiceops.org> wrote: > > > > On Oct 24, 2023, at 9:13 PM, Peter Beckman via VoiceOps < > voiceops@voiceops.org> wrote: > > > > CAUTION:

Re: [VoiceOps] Voice Peering

> On Oct 24, 2023, at 9:13 PM, Peter Beckman via VoiceOps > wrote: > > CAUTION: This email originated from outside of Crocker. Do not click links > or open attachments unless you recognize the sender and know the content is > safe. > > > The challenge is how do you authenticate the end "c

Re: [VoiceOps] Voice Peering

The challenge is how do you authenticate the end "carrier" or service provider? Sure, anyone who leases numbers directly from NANPA can look up the carrier of record and exchange traffic directly, but any business who also leases numbers INDIRECTLY gets cut out and still needs to pay their upstre

Re: [VoiceOps] Voice Peering

We need BGP for VoIP! Wait no that's worse... /s Jokes aside, my understanding of the way people do VoIP routing for private peer interconnection is by looking up the OCN at call time and routing on that. That way you don't have to worry about verifying individual numbers, or keeping routing/owner

Re: [VoiceOps] Voice Peering

I think schemes like DUNDI (and some of the others mentioned here) suffer from a trust issue – what’s to prevent operator X from poisoning the protocol with bogus “stolen” numbers? On Tue, Oct 24, 2023 at 5:25 PM Jared Smith via VoiceOps < voiceops@voiceops.org> wrote: > On Tue, Oct 24, 2023 at

Re: [VoiceOps] Voice Peering

On Tue, Oct 24, 2023 at 8:49 AM Mike Hammett via VoiceOps < voiceops@voiceops.org> wrote: > This was in another thread, but I broke it out into it's own conversation. > Someone had asked: > > --- > I am joining this thread late, but, would anyone out there be interested > in exchanging traffic wit

Re: [VoiceOps] Voice Peering

Brian From: VoiceOps on behalf of Alex Balashov via VoiceOps Sent: Tuesday, October 24, 2023 12:07 PM To: VoiceOps Subject: Re: [VoiceOps] Voice Peering I think that, as has always been the case with these ideas, fascinating technical intricacies miss the fores

Re: [VoiceOps] Voice Peering

ed...@eguy.org) >From: VoiceOps on behalf of Pinchas Neiman > via VoiceOps > Date: Tuesday, October 24, 2023 at 10:45 AM > To: chris > Cc: voiceops > Subject: Re: [VoiceOps] Voice Peering > Maybe the signup fee, and lookup time is what killed the idea? > If that&#x

Re: [VoiceOps] Voice Peering

eek, drop me an email. ( > ed...@eguy.org) > > > > > > *From: *VoiceOps on behalf of Pinchas > Neiman via VoiceOps > *Date: *Tuesday, October 24, 2023 at 10:45 AM > *To: *chris > *Cc: *voiceops > *Subject: *Re: [VoiceOps] Voice Peering > > Mayb

Re: [VoiceOps] Voice Peering

of Pinchas Neiman via VoiceOps Date: Tuesday, October 24, 2023 at 10:45 AM To: chris Cc: voiceops 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 sign

Re: [VoiceOps] Voice Peering

.com >> >> o: (713) 861-4005 >> >> c: (713) 201-1262 >> >> sip:mgra...@mjg.onsip.com >> >> >> >> *From:* VoiceOps *On Behalf Of *Mike >> Hammett via VoiceOps >> *Sent:* Tuesday, October 24, 2023 9:29 AM >> *To:* Pinchas

Re: [VoiceOps] Voice Peering

chris Sent: Tuesday, October 24, 2023 9:36 AM To: Michael Graves Cc: Mike Hammett ; Pinchas Neiman ; VoiceOps Subject: Re: [VoiceOps] Voice Peering +1 enum was great stuff Here in NYC early 2000s we had Stealth doing the VPF (voice peering fabric) https://www.channelfutures.com/teleph

Re: [VoiceOps] Voice Peering

: (713) 861-4005 > > c: (713) 201-1262 > > sip:mgra...@mjg.onsip.com > > > > *From:* VoiceOps *On Behalf Of *Mike > Hammett via VoiceOps > *Sent:* Tuesday, October 24, 2023 9:29 AM > *To:* Pinchas Neiman > *Cc:* VoiceOps > *Subject:* Re: [VoiceOps] Voice Peering > >

Re: [VoiceOps] Voice Peering

p:mgra...@mjg.onsip.com From: VoiceOps On Behalf Of Mike Hammett via VoiceOps Sent: Tuesday, October 24, 2023 9:29 AM To: Pinchas Neiman Cc: VoiceOps Subject: Re: [VoiceOps] Voice Peering https://wirevolution.com/step-8-register-your-phone-number-at-e164org/ Most of the links have died, so that id

Re: [VoiceOps] Voice Peering

Message - From: "Pinchas Neiman via VoiceOps" To: "Alex Balashov" Cc: "VoiceOps" 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 neve

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

Re: [VoiceOps] Voice Peering

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 any

[VoiceOps] Voice Peering

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

Re: [VoiceOps] Voice peering

I concur on the ENUM solution being obsolete. Sure it was better than TCAP, but not as flexible as a 302. Its appeal originally was a centralized phone number ownership lookup but it was never deployed that way; DNS is too slow at updating information and too open

Re: [VoiceOps] Voice peering

From my perspective as an implementor down in the weeds, ENUM is just a failure-prone moving part and a source of unnecessary complexity at this point. DNS is not a particularly good transport vehicle for data queries. As far as I can tell, the industry went in that direction at the time it did

Re: [VoiceOps] Voice peering

est Internet Exchange > http://www.midwest-ix.com > > > > -- > *From: *"Ross Tajvar" > *To: *"VoiceOps" > *Sent: *Tuesday, January 5, 2021 7:57:12 AM > *Subject: *[VoiceOps] Voice peering > > Based on this presentation [0] from Comcast, they are interco

Re: [VoiceOps] Voice peering

- Original Message - From: "Ross Tajvar" To: "VoiceOps" Sent: Tuesday, January 5, 2021 7:57:12 AM Subject: [VoiceOps] Voice peering Based on this presentation [0] from Comcast, they are interconnecting with their biggest voice peers via SIP rather than SS7. They

[VoiceOps] Voice peering

Based on this presentation [0] from Comcast, they are interconnecting with their biggest voice peers via SIP rather than SS7. They appear to use ENUM for route selection. I'm sure others are doing this too, though I can't find anything public. I'm interested if anyone has more info on how this wor