I know there are plenty of threads with the term “quality” but I am hoping to collaborate with the community to build shared knowledge on troubleshooting.
We’ve been receiving intermittent complaints about video/audio quality on reasonably sized bridges (e.g. 3-8 people) where the users are falling back to Google Meet and not having the same issues.
Inevitably some users of any conferencing platform will have poor internet connections or client side issues that will impact quality but it seems other products are able to compensate for this (or at least thats the perception).
In the last couple of weeks we’ve deployed rtcstats and Elastic APM to help us understand what’s happening. I am working through mountains of data to identify insights, mainly focused on the following at the moment:
- Making sense of huge amounts of RTCSTATS data, utilizing a lot of fippo’s great work.
- Looking at network factors, including QoS, jitter and latency how they influence rtc.
- Comparing configuration and packet captures between conferences on how our implementation and meet.jit.si
Does anyone have any tips or tricks, anything you can share with myself and the community that will help on this journey?
(I plan to share back for what I learn along this long and dark journey)