Open Bug 1641319 Opened 4 years ago Updated 4 years ago

When joining from different systems into a specific jump.chat meeting room, some participants don't see each other while some see more

Categories

(Core :: WebRTC: Networking, defect, P3)

Desktop
Unspecified
defect

Tracking

()

Tracking Status
firefox76 --- affected
firefox77 --- affected
firefox78 --- affected

People

(Reporter: danibodea, Unassigned)

References

Details

Note

  • When multiple different systems join a jump.chat meeting room, an inconsistency with the participants seen as attending in the room will be observed between the call participants; some participants may be hidden to others while some don't see any other participants.

Affected versions

  • nightly v78.0a1
  • beta v77.0 (RC)
  • release v76.0.1

Affected platforms

  • it appears to be somewhat related to the system, not the platform/OS

Steps to reproduce

  1. Engage in a jump.chat meeting room between a few different systems.
  2. Share the microphone and camera between them.

Expected result

  • All the call participants can see/hear each other.

Actual result

  • observe that one system sees 3/4 participants, 2 systems don't see each other, but both see the first one and a fourth one would rarely connect to one of the others

Additional notes

  • It should be mentioned that it is not a platform-dependent issue, as there were discrepancies between the results, but the connectivity does appear to be somewhat consistent between certain systems.
  • The results were consistent with the behavior seen in Chrome browser between the same systems and across the 3 main firefox channels.
  • This may be an issue of the web-app, but the issue is also logged for future test results and tracking purposes.
  • the issue was also reported on their feedback form, but no ticket was provided after submission.

S1 or S2 bugs need an assignee - could you find someone for this bug?

Flags: needinfo?(docfaraday)

So, given that the same sort of problem occurs on Chrome (according to the description, correct me if this is wrong), I'd call this an S3.

Severity: S2 → S3
Flags: needinfo?(docfaraday)
Priority: -- → P3
See Also: → 1646048
No longer blocks: 1646048
You need to log in before you can comment on or make changes to this bug.