Open Bug 1600698 Opened 3 years ago Updated 3 days ago

[JITSI] bandwith usage and status info


(Core :: WebRTC, enhancement, P3)




Tracking Status
firefox-esr68 --- affected
firefox71 --- wontfix
firefox72 --- wontfix
firefox73 --- wontfix
firefox74 --- wontfix
firefox75 --- affected
firefox76 --- affected
firefox77 --- affected


(Reporter: leorthur, Unassigned)




(Keywords: site-compat, Whiteboard: [jitsi-meet][wfh])

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Go to and make a new conference call with many people

Actual results:

Bandwidth is more important than chromium.
It is like connections are not terminated sometimes.

There is an info box on all jitster guy but there isn't any information about bandwidth speed.

Expected results:

bandwidth should be reasonable, the information box on jitster guy should work to see incoming and outgoing speed.

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

I can confirm that this issue is reproducible on the latest Nightly 73.0a1, Firefox 72 beta 2 and Firefox 71.

Component: Untriaged → WebRTC
Ever confirmed: true
Product: Firefox → Core
Version: 69 Branch → Trunk

From an email thread with Emil Ivov at jitsi, it sounds like bandwidth adaptation is broken between Firefox and jitsi and will be until we support transport-cc. Setting as P3 for now until I have a better idea of where this is on our roadmap.

Priority: -- → P3


Would be great that Firefox can make work jitsi properly.

A lot of company use Firefox and don't want to use chromium or chrome.


See Also: → 1606823

Depends on bug 1606823 based on comment #2

Depends on: 1606823
Keywords: site-compat
Whiteboard: [jitsi-meet]
See Also: 1606823
Whiteboard: [jitsi-meet] → [jitsi-meet][wfh]

It looks Firefox 78 now indicates bandwidth. A test with a low bandwidth connection would be useful to see if video resolution changes automatically.

Severity: normal → S3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.