[VoiceOps] Voice Peering

Michael Graves mgraves at mstvp.com
Wed Oct 25 15:12:12 EDT 2023


Alex,

The apparent elegance of a technology can be entrancing.

To quote the great Leonard Cohen, "We're blinded by the beauty of our weapons."

Michael Graves
mgraves at mstvp.com
o: (713) 861-4005
c: (713) 201-1262
sip:mgraves at mjg.onsip.com

-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Alex Balashov via VoiceOps
Sent: Wednesday, October 25, 2023 2:01 PM
To: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Voice Peering


> On 25 Oct 2023, at 11:18, Pinchas Neiman via VoiceOps <voiceops at voiceops.org> 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) Practically implementing STIR/SHAKEN has bureaucracy involved.

Just this. The technical specs are the easy part. Actually implementing is mostly a clerical and bureaucratic chore. 
There is also widespread misunderstanding of what it does and does not accomplish. It does not prevent spam calls. 

-- Alex

--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops


More information about the VoiceOps mailing list