Project

General

Profile

Actions
Copy link

action #116959

closed

Unreliable/unusable audio connections using Jitsi instance on meet.opensuse.org from Android clients size:S

Added by okurz about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
okurz
Target version:
openQA Project (public) - Ready
Start date:
2022-09-21
Due date:
% Done:

0%

Estimated time:
Tags:
reactive work

Description

Observation

Reported in https://suse.slack.com/archives/C02CU9CL6FQ/p1663760551006499

Hi. I have observed a reproducible problem today with meet.opensuse.org vs. meet.jit.si . When I join with the Android Jitsi App (22.5.1) from my Smartphone on meet.opensuse.org I can not reliably hear participants and they can not reliably hear me. Reconnecting helps in some but not all cases. The same problem does not appear with meet.jit.si. I suspect that meet.jit.si runs a more recent Jitsi server version and hence is not showing this problem. Can you confirm that meet.opensuse.org runs an older version than meet.jit.si? If yes, what are the plans to update?

Impact

meet.opensuse.org is not usable when participants want to join our usual SUSE QE Tools meetings from phone

Suggestions

  • Report problem with meet.opensuse.org to according administrators and await their reaction regarding server version and potential upgrade
  • Install an older version on Android (e.g. F-Droid normally has older versions selectable)

Workaround

Use https://meet.jit.si, in particular for SUSE QE tools meetings https://meet.jit.si/suse_qa_tools

Files

Download all files
Screenshot_20220928-100635.png (92.8 KB) Screenshot_20220928-100635.png this is how the Android client looks like in an active meeting on meet.opensuse.org wrongly showing every member as muted, no video and nothing audible okurz, 2022-09-28 08:09
Screenshot_20220928-101240.png (832 KB) Screenshot_20220928-101240.png Showing active session on meet.jit.si, working okurz, 2022-09-28 08:13
Actions
Copy link
 #1

Updated by okurz about 2 years ago

Leon Schroeder has confirmed the issue writing

Just stumbled upon this this morning, too...

and they plan to update so we should wait for that.

Actions
Copy link Download all files
 #2

Updated by okurz about 2 years ago

Problem seems to persist. Attached two screenshots of Screenshot_20220928-100635.png on meet.opensuse.org as well as meet.jit.si where Screenshot_20220928-101240.png

Actions
Copy link
 #3

Updated by okurz about 2 years ago

  • Due date changed from 2022-10-07 to 2022-10-21

On https://meet.jit.si/suse_qa_tools people multiple time were dropped and struggled to rejoin. We dynamically switched to https://meet.opensuse.org/suse_qa_tools in those cases. I asked again about any planned updates in https://suse.slack.com/archives/C02CU9CL6FQ/p1664963937870849?thread_ts=1663760551.006499&cid=C02CU9CL6FQ

(Oliver Kurz) We currently still use https://meet.jit.si/ where people multiple time were dropped and struggled to rejoin. We dynamically switched to https://meet.opensuse.org/ in those cases which (likely) still has the above problems. Any update on the "planned upgrade"?

EDIT: An alternative was mentioned that we could try out: https://meet-test.opensuse.org/suse_qa_tools

Actions
Copy link
 #4

Updated by okurz about 2 years ago

I just tried meet-test.opensuse.org with the Android client and it behaves slightly better than meet.opensuse.org but worse than meet.jit.si . All users still show up as muted but I can hear them and they can hear me. On meet.jit.si the status of people is properly reflected, unmuted and audible

Actions
Copy link
 #5

Updated by okurz about 2 years ago

  • Due date changed from 2022-10-21 to 2022-11-18

There was no change. We need to stay on meet.jit.si for now

Actions
Copy link
 #6

Updated by mkittler about 2 years ago

  • Subject changed from Unreliable/unusable audio connections using Jitsi instance on meet.opensuse.org from Android clients to Unreliable/unusable audio connections using Jitsi instance on meet.opensuse.org from Android clients size:S
  • Description updated (diff)
Actions
Copy link
 #7

Updated by okurz about 2 years ago

We can try to use a downgraded Android client, e.g. from f-droid

Actions
Copy link
 #8

Updated by livdywan about 2 years ago

okurz wrote:

We can try to use a downgraded Android client, e.g. from f-droid

Did you try if that works? Personally I only use the web app which isn't affected.

Actions
Copy link
 #9

Updated by okurz about 2 years ago

  • Due date changed from 2022-11-18 to 2023-03-31
  • Priority changed from Normal to Low

cdywan wrote:

okurz wrote:

We can try to use a downgraded Android client, e.g. from f-droid

Did you try if that works? Personally I only use the web app which isn't affected.

No, I did not try. However yesterday we tried again all three instances and meet.jit.si was fine, meet-test was fine as well, moo still not so I assume testing is still going on with the test instance

Actions
Copy link
 #10

Updated by okurz almost 2 years ago

  • Due date deleted (2023-03-31)
  • Status changed from Feedback to Resolved

Whenever I try meet.opensuse.org lately it still shows the problem. I think we will just have to accept that meet.jit.si works for us. Eventually in case it would show problems we could try to switch to meet.opensuse.org anyway. I don't think we need this ticket for further tracking.

Actions
Copy link

Also available in: Atom PDF