Closed Bug 1644577 Opened 4 years ago Closed 4 years ago

Jitsi communication broken after bug 1641600

Categories

(Core :: WebRTC: Signaling, defect, P1)

79 Branch
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr68 --- unaffected
firefox77 --- unaffected
firefox78 --- unaffected
firefox79 --- fixed

People

(Reporter: philipp, Assigned: dminor)

References

(Regression)

Details

(Keywords: regression, site-compat)

Attachments

(1 obsolete file)

after bug 1641600 landed in 79.0a1 i can no longer open up a communication channel on jitsi with another user (i've observed this under win10 & don't know if other platforms are affected).

str for me:

  • enter https://meet.jit.si/randomfxtest on a device and give permission to access the webcam
  • enter the same url from a different device (in my case it has no cam, only a microphone - not sure if this matters for reproducing the issue)
  • on each device i can see that there is another participant in the room, but it's displayed as muted and no sound or picture is received from the remote device

I am not able to reproduce this on 79.0a1 (2020-06-09). I have tried between two machines (Linux and OS X):
Nightly to Nightly,
Nightly to Chrome,
Nightly to Release.
I am getting low bandwidth warnings, which I do not suspect is an issue on my end.

philipp, could you add what the setup is on your second device?

Flags: needinfo?(madperson)

both of the devices run windows 10.
i first observed the issue with current nightly to current 68esr (each in a different network) but can also repro nightly to nighly in the same LAN.

Flags: needinfo?(madperson)

I can reproduce under Windows 10 if and only if I have no camera. I will see if the same thing happens on Linux, though I am unable to test on OS X without a camera.

This reproduces on Linux without a camera.

I can confirm that adding ,*.jit.si to the media.peerconnection.video.use_rtx.blocklist preference corrects the issue.

Assignee: nobody → na-g
Status: NEW → ASSIGNED

Dan, I have added a commit to add *.jit.si to the blocklist. If you want to land that while looking for the issue feel free.

Assignee: na-g → dminor
Severity: -- → S2
Priority: -- → P1
Severity: S2 → S3

With RTX enabled in Firefox, I'm seeing RTX codecs but no ssrc-group in the SDP coming from Jitsi. In the past, this has been problematic in Firefox, so I'm going to try to make Firefox more tolerant of this situation as a workaround. Oddly, with RTX disabled in Firefox, Jitsi offers RTX with a suitable ssrc-group.

Jitsi has found a bug on their side and will be committing a fix today. I'll retest this tomorrow and close if things look good.

Jitsi bug as been fixed, it should be available in the next release of https://meet.jit.si

I think there are two separate problems. I'm having the same symptoms on whereby.com with RTX enabled if the only input device is a microphone. So I think there was a bug on the Jitsi side, which is now fixed (thanks Jaya!), but there is still a problem with Firefox itself. I'll look into it.

On Jitsi and whereby.com, the problem only seems to occur if the other party is Chrome.

This is now working for me on https://beta.meet.jit.si. I still think there might be something going on with direct Firefox <-> Chrome calls, or it might just be a issue with my local testing set up. I'm going to resolve this bug, and I'll open a separate bug if I continue to see problems on whereby.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Has Regression Range: --- → yes
Attachment #9155531 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: