From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] reality2 podcast
Date: Thu, 23 Sep 2021 11:24:28 -0400 [thread overview]
Message-ID: <16333D74-1FEC-4CAD-A29D-2C5D0275332F@jonathanfoulkes.com> (raw)
In-Reply-To: <CAA93jw7TxhNn1201QbnsTd8hQf+TgFquwiEJ2Bqt6Hvcaaq7DA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
I’ll note that I defected what seemed to be a bloated line from Doc’s end. Voice quality was nowhere near as good as it could be.
Podcasters should A) use a wired connection for local connections, and B) run a well-tuned AQM on their router.
Running this VoIP quality test would be a good proxy for line latency performance for conference calls (voice only).
https://www.ringcentral.com/support/qos.html <https://www.ringcentral.com/support/qos.html>
Attached are two images of results of that test on two of my lines, both sore the same MOS rating of 4.2.
The first is a cable line with 30MBps of uplink capacity, with an IQrouter Pro.
the second is my backup 10 / 0.7Mbps DSL Line with an IQrouter v3, note how this graph and stats is almost identical to the cable line, some stats are actually better on DSL.
Friends don’t let friends VoIP/Zoom without Cake ;-)
Cheers,
Jonathan
> On Sep 17, 2021, at 2:27 PM, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>
> My nuanced personal tale of the aqm deployment debate, with a
> modest starlink WIP update, and a reference to my fav outcomes of the iab
> workshop, just went up here:
>
> https://reality2.substack.com/p/improving-the-internets-responsiveness <https://reality2.substack.com/p/improving-the-internets-responsiveness>
>
>
> --
> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2.1: Type: text/html, Size: 3342 bytes --]
[-- Attachment #2.2: VoIPTest_WS35Up_line.png --]
[-- Type: image/png, Size: 132391 bytes --]
[-- Attachment #2.3: VoIPTest_DSLline.png --]
[-- Type: image/png, Size: 136763 bytes --]
next prev parent reply other threads:[~2021-09-23 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 18:27 Dave Taht
2021-09-17 19:09 ` Gabe Kassel
2021-09-22 20:15 ` Jonathan Foulkes
2021-09-23 15:24 ` Jonathan Foulkes [this message]
2021-09-23 15:55 ` [Bloat] quality podcasting metrics Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16333D74-1FEC-4CAD-A29D-2C5D0275332F@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox