Hi David-
I second. Although encapsulation can have its own issues, one we see
often is RTP packet rates not matching timestamps, sometimes up to 10%
off (media/announcement servers are typical offenders). But that can
be unraveled and is not a config issue.
-Jeff
Quoting "Hiers, David via VoiceOps" <voiceops@voiceops.org>:
Well... yeah, kinda-sometimes maybe.
If any network device has any code that is SIP/RTP aware, that code
can be poorly configured or make a mistake. Hiding SIP/RTP inside
anything else is one way to avoid being seen by bad configs or buggy
code.
A VPN can't prevent backhoe drivers from digging up your fiber, but
it can maybe prevent keyboard drivers from munging your packets.
It's not a guaranteed fix, but it is one more RFC-3093-ish card you
can play that might help in some scenarios.
David
-----Original Message-----
From: VoiceOps <voiceops-boun...@voiceops.org> On Behalf Of Alex
Balashov via VoiceOps
Sent: Friday, March 8, 2024 5:33 AM
To: VoiceOps <voiceops@voiceops.org>
Subject: [EXTERNAL] Re: [VoiceOps] One Way Audio - Frontier Comm
(Los Angeles area)
Caution: External email - Please use caution opening links and
attachments from external senders
On 8 Mar 2024, at 08:32, Mike Hammett via VoiceOps
<voiceops@voiceops.org> wrote:
I don't trust last mile networks to reliably deliver SIP calls. I
usually end up putting them into VPNs, TLS, etc.
VPNs and TLS make last-mile networks more reliable? :-)
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
_______________________________________________
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
