If it's not already obvious, I would like to mention that jitter/buffering on video is just about a non-issue (otherwise Microsoft Teams wouldn't exist) - but for audio it is everything.
Users will notice 20ms of audio delay as a lip sync issue on a streaming movie, but for videoconferencing the focus is on the message and not the medium. Separate the streams if you can, and treat them separately. The other nifty trick at the DSLAM level was to tweak interleaving settings so that voice had a nice and consistent latency, as a substitute for per-PVC settings the chipsets got to the point where they could map ethernet priority tags to differentiated configs - but I appreciate that there is probably nobody left with access to those settings! John On Wed, 20 Sept 2023 at 09:31, Dave Taht <dave.t...@gmail.com> wrote: > Occasionally I question my baseline numbers, and struggle to find cites to > support my increasingly ancient viewpoint, which goes back to CISCO LLQ, if > not earlier. > > Recently this question came up that I lack an answer to, and was wondering > what operators thought was the right number, and wondering how y´all > achieve it. Taking a poll over here, > with the core question being 10ms,30ms,100ms or 200ms: > > https://www.linkedin.com/feed/update/urn:li:activity:7110029609559056384/? > > -- > Oct 30: > https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html > Dave Täht CSO, LibreQos > _______________________________________________ > AusNOG mailing list > AusNOG@lists.ausnog.net > https://lists.ausnog.net/mailman/listinfo/ausnog >
_______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net https://lists.ausnog.net/mailman/listinfo/ausnog