Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-11 Thread Nathan Anderson via VoiceOps
11, 2024 6:39 PM To: Nathan Anderson Cc: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) Hi Nathan- > I mean, maybe if you are aggregating audio transmissions into > 150ms+ sized frames, but...that seems like a bad idea? It's not a goo

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-11 Thread Jeff Brower via VoiceOps
quot;change my mind"; heh.   -- Nathan   FROM: VoiceOps [mailto:voiceops-boun...@voiceops.org] ON BEHALF OF Pinchas Neiman via VoiceOps SENT: Sunday, March 10, 2024 7:29 AM TO: Alex Balashov CC: VoiceOps SUBJECT: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles a

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-11 Thread Nathan Anderson via VoiceOps
eops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) Hi Nathan- > In short, I have a hard time believing that MTU issues are the underlying > cause for many (or even any) VoIP audio delivery problems Only if it was encapsulated over some form of TCP. > VoIP

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-11 Thread Jeff Brower via VoiceOps
ON BEHALF OF Pinchas Neiman via VoiceOps SENT: Sunday, March 10, 2024 7:29 AM TO: Alex Balashov CC: VoiceOps SUBJECT: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) I have (on a rural area DSL line) a desk phone registered directly on line 1, and line 2 over the VPN, whenev

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-11 Thread Nathan Anderson via VoiceOps
ps Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) I have (on a rural area DSL line) a desk phone registered directly on line 1, and line 2 over the VPN, whenever someone on line 1 tells me I couldn't hear you well, I am saying calling you back with another line,

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-11 Thread Glen Gerhard via VoiceOps
oiceOps" *Sent: *Saturday, March 9, 2024 7:57:33 AM *Subject: *Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) No, it's true, consider me appropriately humbled. I underappreciated the nuance of this issue. I thought we were talking about something closer to the physicality of

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-10 Thread Mike Hammett via VoiceOps
ceOps" To: "VoiceOps" Sent: Saturday, March 9, 2024 7:57:33 AM Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) No, it's true, consider me appropriately humbled. I underappreciated the nuance of this issue. I thought we were talking about something closer

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-10 Thread Pinchas Neiman via VoiceOps
I have (on a rural area DSL line) a desk phone registered directly on line 1, and line 2 over the VPN, whenever someone on line 1 tells me I couldn't hear you well, I am saying calling you back with another line, every time they will respond immediately Ah. Now your voice is much better. TCP

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-09 Thread Alex Balashov via VoiceOps
No, it's true, consider me appropriately humbled. I underappreciated the nuance of this issue. I thought we were talking about something closer to the physicality of networks, not packet inspection/filtering/etc. -- Alex > On 9 Mar 2024, at 08:11, James Cloos wrote: > >> "AB" == Alex

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-09 Thread James Cloos via VoiceOps
> "AB" == Alex Balashov writes: >> I don't trust last mile networks to reliably deliver SIP calls. I usually >> end up putting them into VPNs, TLS, etc. AB> VPNs and TLS make last-mile networks more reliable? :-) on the vpn side, wireguard (which runs over udp) certainly does. I imagine

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Jim Rodgers via VoiceOps
tomers > and encapsulating the whole enchilada -- SIP, RTP, and all -- within a VPN > would actually be a pretty interesting experiment... > > > > -- Nathan > > > > *From:* VoiceOps [mailto:voiceops-boun...@voiceops.org] *On Behalf Of *Jim > Rodgers via VoiceOp

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Nathan Anderson via VoiceOps
: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) We just set up a VPN from one of our customers to our data center and the audio issue is gone as the traffic is going over the VPN. So VPN does resolve the problem. Jim On Fri, Mar 8, 2024 at 07:45 Nathan Anderson via VoiceOps

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Jim Rodgers via VoiceOps
iment... > > > > -- Nathan > > > > *From:* VoiceOps [mailto:voiceops-boun...@voiceops.org] *On Behalf Of *Jim > Rodgers via VoiceOps > *Sent:* Friday, March 8, 2024 7:09 AM > *To:* Mike Hammett > *Cc:* voiceops@voiceops.org > *Subject:* Re: [VoiceOps] One

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Nathan Anderson via VoiceOps
In this age of AI, why would we be surprised when the machines try to talk to us... :-) -Original Message- From: Brian :: [mailto:b...@iptel.co] Sent: Friday, March 8, 2024 9:06 AM To: Nathan Anderson Cc: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Brian :: via VoiceOps
Never send a human to do a machine's job. > On 8 Mar 2024, at 17:01, Nathan Anderson via VoiceOps > wrote: > > Or there was an actual payload inside with an English text string? ___ VoiceOps mailing list VoiceOps@voiceops.org

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Nathan Anderson via VoiceOps
From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Kent A via VoiceOps Sent: Friday, March 8, 2024 8:51 AM To: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) ICMP I would have noticed right away. I thought we were screaming

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Kent A via VoiceOps
functionality has been restored. -Kent From: VoiceOps On Behalf Of Nathan Anderson via VoiceOps Sent: Friday, March 8, 2024 11:47 AM To: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) "but I did get TCP rejections to my inbound UDP pa

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Ethan Clay via VoiceOps
t { font-size: 10pt } div.zm_7208056706780523974_parse_3217461976481657867 div.x_1296020992WordSection1 { }  From: VoiceOps On Behalf Of Nathan Anderson via VoiceOpsSent: Friday, March 8, 2024 11:47 AMTo: voiceops@voiceops.orgSubject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) "but I did get TCP rejections to my i

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Kent A via VoiceOps
From: VoiceOps On Behalf Of Nathan Anderson via VoiceOps Sent: Friday, March 8, 2024 11:47 AM To: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) "but I did get TCP rejections to my inbound UDP packets" ? Did you mean yo

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Nathan Anderson via VoiceOps
On Behalf Of Kent A via VoiceOps Sent: Friday, March 8, 2024 7:55 AM To: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) I too have a customer in the same area with the same exact problem. However they are doing SIP over UDP, and initially inbound S

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Kent A via VoiceOps
: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) Assuming I understood the original problem description accurately, I don't see how a lossy trunk somewhere could explain 100% loss of *just* RTP and only in *one* specific direction with *zero* impact to any other internet

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Nathan Anderson via VoiceOps
...@voiceops.org] On Behalf Of Jim Rodgers via VoiceOps Sent: Friday, March 8, 2024 7:09 AM To: Mike Hammett Cc: voiceops@voiceops.org Subject: Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) We use SIP TLS. I don't think they're intentionally blocking voice traffic, I think there's

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Jim Rodgers via VoiceOps
et Exchange > http://www.midwest-ix.com > > > > -- > *From: *"Jim Rodgers via VoiceOps" > *To: *voiceops@voiceops.org > *Sent: *Thursday, March 7, 2024 11:16:23 AM > *Subject: *[VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) > >

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Alex Balashov via VoiceOps
> On 8 Mar 2024, at 08:44, Mike Hammett wrote: > > In my experience, yes. Well, at least the reliable delivery of my voice > traffic. Whether intentional or mistake (I'm hoping the latter), I've had > random reliability on some major last mile networks. Never a problem when one > of the

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Mike Hammett via VoiceOps
Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com - Original Message - From: "Alex Balashov via VoiceOps" To: "VoiceOps" Sent: Friday, March 8, 2024 7:33:25 AM Subject: Re: [VoiceOps] One Way Audio - Frontier Co

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Alex Balashov via VoiceOps
> On 8 Mar 2024, at 08:32, Mike Hammett via VoiceOps > 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

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-08 Thread Mike Hammett via VoiceOps
t;Jim Rodgers via VoiceOps" To: voiceops@voiceops.org Sent: Thursday, March 7, 2024 11:16:23 AM Subject: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area) Beginning early yesterday, we're seeing dropped voice rtp traffic to some of our business customers in the Los Angeles

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-07 Thread Jim Rodgers via VoiceOps
Yeah, I posted to nanog, but didn't receive a response. I'll try the email address you sent. Thanks... Jim On Thu, Mar 7, 2024 at 1:25 PM Ross Tajvar wrote: > You could try emailing noc@ftr.com or asking on NANOG. > > On Thu, Mar 7, 2024, 12:16 PM Jim Rodgers via VoiceOps < >

Re: [VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-07 Thread Ross Tajvar via VoiceOps
You could try emailing noc@ftr.com or asking on NANOG. On Thu, Mar 7, 2024, 12:16 PM Jim Rodgers via VoiceOps < voiceops@voiceops.org> wrote: > Beginning early yesterday, we're seeing dropped voice rtp traffic to some > of our business customers in the Los Angeles metro area on Frontier Comm

[VoiceOps] One Way Audio - Frontier Comm (Los Angeles area)

2024-03-07 Thread Jim Rodgers via VoiceOps
Beginning early yesterday, we're seeing dropped voice rtp traffic to some of our business customers in the Los Angeles metro area on Frontier Comm broadband fiber. The voice udp stream is leaving our data center and never making it to the Frontier fiber customer. It's not all of our customers,