Sometimes participants can't hear other participants #5230

jonnius · 2020-03-18T14:39:03Z

Description

Sometimes some participants can't hear some other participants. Some findings:

occurs more often in meetings with many participants (does not seem to occur with 4 participants, occurs a lot with >=7 participants)
does not happen between users with camera enabled
is not necessarily bidirectional (A might hear B, while B does not hear A)
workarounds
- in most cases one can work around the issue by toggling the camera
- in some cases one can work around the issue by reloading the page
- in some cases none of the workarounds above helps
issue seems to be around for years already, as it might be a duplicate to the closed issues Audio problems #1278 and Audio lost for some recipients #641

Current behavior

There is an audio-only meeting with n>7 participants. Some participants cannot hear all other participants, e.g. participant 4 cannot hear participant 3 and 7.

Expected Behavior

Every participant can hear every other participant.

Possible Solution

Steps to reproduce

Start a Jitis Meeting with as many users as possible, only enable Audio and try to speak to each other.

Environment details

Version: jitsi-meet v1.0.4101-1
Browsers tested: Chrome, Firefox on Win10 and Ubuntu 16.04

rettichschnidi · 2020-03-19T23:22:48Z

Pretty sure this is related to #4758

Also, other users (including me) have the same problem:

damencho · 2020-03-19T23:27:42Z

Is Firefox involved?

rettichschnidi · 2020-03-20T03:28:37Z

Yes
We could test again without Firefox, but it is very unlikely that we can get all our users to not use Firefox.

damencho · 2020-03-20T09:48:24Z

We are working on improving Firefox experience, but that is for now. Firefox sometimes does not send or receive any streams ... and leads to problems. That's why we put a notification when you are on Firefox and using meet.jit.si, to warn people.

jonnius · 2020-03-20T13:54:37Z

We experienced the issues also on Chrome.

We just updated to jitsi-meet v1.0.4296-1 and disabled Peer-to-Peer connections. On a test with 10 participants the issue did not occur on Chrome any more. On a test with everyone on Firefox 1 out of 10 could not hear some others.

damencho · 2020-03-20T15:15:10Z

We will update very soon stable.

Jasper-Ben · 2020-03-23T12:08:23Z

We are experiencing the same issue with 9 people in the same room, even between users using chromium-based browsers. We also tried to connect with all participants using said browsers (which I'm 90% sure we archived) and issues still persists. So maybe not just a firefox issue?

jonnius · 2020-03-23T13:19:03Z

We did as well before updating. Which version are you using?

Jasper-Ben · 2020-03-23T13:51:12Z

the latest jitsi-meet package currently available from jitsis debian repository: jitsi-meet/stable,now 1.0.4101-1

It used to work when microphone and cam where enabled by default when joining a room during our testing phase. But since we disabled that in the jitsi server settings it is completely unreliable. So for me it seems the issue is related to the (lack of) video or audio streaming.
Out of privacy concerns I am unfortunately unable to reactivate said settings to see if it makes any difference, as 20+ users in our company now expect it to be disabled by default.

Also I was able to reproduce the issue in a two-participants room (although one was using firefox), so this issue does not seem to be bound to the number of users in a room as suggested in the initial report. There might have been users in other rooms at that time though, so it might be a question of how many users are connected in general, regardless of room.
The two of us then switched to my private jitsi instance without disabled devices by default and it worked as expected.

jonnius · 2020-03-23T13:57:38Z

You are using the very same version we experienced this issue a lot with. After updating to the 4296 build we did not see this issue on Chrome any more. We also have mic and cam disable by default.

Jasper-Ben · 2020-03-23T14:04:08Z

thanks for the info! will try the nightly branch then and install the same version. I will report back, if we continue to experience issues.

jonnius · 2020-03-24T09:09:05Z

We just had a meeting with 11 participants, all on Chrome, where one participant could not be heard by some others. Reloading the page for the one fixed it. Build: 4296

saghul · 2020-03-24T11:16:05Z

Thanks for chiming in @jonnius !

Jasper-Ben · 2020-03-24T11:35:04Z

We just had a test meeting with 20 participants (all on chromium) and it worked flawlessly. Also build 4296. Seems to be fixed 👍

Jasper-Ben · 2020-03-24T11:55:14Z

P.S.: we actually had one minor issue with a participant using Vivaldi. After he switched to chrome it worked as expected. We didn't investigate further but my guess would be that Vivaldi might use an old chromium base. Just something to be aware of.

Isolator70 · 2020-03-24T20:44:16Z

Hello, using Jitsi sporadically, but due to Corona crisis now more often.
Today I had a 2 person call between Chromium@LinuxMint_18.3_PC and Jitsi App@Android. Everything fully up-to-date. After some minutes it was not possible anymore for the Person at Android to hear the Person from the PC.
At the PC one could observe, that the microphone indicator did not react to volume put into the microphone.
Going to the settings of Jitsi in Chromium browser one could see "Permission not granted" for the audio stuff (although it was done and checked at the beginning of the meeting).
Checking the audio permission in Chromium itself, camera and audio stuff was enabled.
After closing and restarting the meeting everything was fine again, but broke down some minutes later again.
Do you think it is the same issue or shall I create another ticket?
Thank you

Isolator70 · 2020-03-25T11:32:31Z

Okay, I have to add following information: Today I was in a 35 minutes video call with up to 17 participants, most of them without activated camera, 5 with camera activated. I'm sure most of them were on Windows machines, 1 maybe on Mac, 1 with iPhone, 1 with Android,
From my point of view, everything ran perfect - I couldn't see the issue of yesterday again! So I will observe the behaviour if it is random.

keinstein · 2020-04-05T09:18:49Z

Hi, on March 27th, we had a meeting with 3 people on meet.jit.si (I don't know which version they run). All using web browsers and we had the problem that the 3rd person connected but did not receive any audio or video. After he managed to setup his audio and video settings, person 1 could hear both 2 and 3, 2 could hear only 1, 3 only 2. So every one was streaming something to someone. But somehow the streams stopped working.

real-or-random · 2020-04-05T18:22:14Z

We observed this today in 3-person call on 4384. A Jigasi/SIP peer couldn't hear an electron peer. Everything else worked. "Restarting" the stream by changing the microphone device on electron and changing back fixed this.

thomaswucher · 2020-04-28T16:00:29Z

We also observed this problem today on a self-hosted instance using the latest official docker images and the master branch of docker-jitsi-meet (0177765f) in a conference with 5 participants.

All participants were using Firefox. The ones which had video enabled didn't experience the problem, those with audio only could sometimes not hear all other participants. For those experiencing problems, reconnecting sometimes helped.

Jasper-Ben · 2020-04-28T17:37:55Z

All participants were using Firefox.

Hi Thomas, as things stand right now I'd suggest you enforce a policy of chromium based browsers only, as issues with Firefox are still being resolved. And although the related issue #4758 is marked as resolved, this to my understanding only fixes any issues on the jitsi side of things. There are still open upstream issues in Firefox (linked at the bottom of the thread).

We enforce our chromium only policy by changing the following in the interface_config.js:

OPTIMAL_BROWSERS: [ 'chrome', 'chromium', 'nwjs', 'electron' ],
UNSUPPORTED_BROWSERS: ['firefox','safari'],

This causes users trying to open jitsi with a Firefox or Safari Browser to be prompted to install the latest Google Chrome. For anyone who doesn't want to use Chrome out of privacy concerns we recommend using Chromium or Brave, as they are both open-source and (for the most part) do not include the Google tracking stuff.

jonnius · 2020-05-02T18:18:58Z

Things should improve with Firefox 76.

btsimonh · 2020-05-04T17:08:42Z

I'm currently investigating a problem with jitsi which sounds very much like this and previous descriptions.

We had 3 people on the call, All Chrome 81.0.4044.129 on windows 10 64 bit using embedded jitsi from 'https://meet.jit.si/external_api.js'. - So this may highlight that it's not a firefox only issue, and hopefully may provide some more pointers....
Certainly the 'unheard' person was sending audio, because they were heard by another, yet not heard by the third person. The 'unheard' person could hear the person who could not hear them.... The person who could not hear them could hear the other person.

Prior to integrating, we tested 7-10 calls using meet.jit.si for bulk family calls (always with video?), and apart from once on MAC which didn't screenshare whatever we did (it had previously), we had no (apparent) problems.

I find this in the browser log as a yellow:
Logger.js:154 2020-05-04T15:56:33.440Z [modules/statistics/AudioOutputProblemDetector.js] A potential problem is detected with the audio output for participant 02b26f22, local audio levels: [null,null], remote audio levels: undefined

If I separately join the room using meet.jit.si/roomname, then I too could hear the person, but not through the embedded version (could i just have been lucky?). But this was not an extensive test (3 times, it worked).

I start all the instances like this:
(i.e.
video muted; which could be related/
these ones because they mess with my audio mojo (i.e. I'm also recording quality audio from the mic, and these seem to mess with Chrome's global mic gain).
enableNoisyMicDetection:false, - I don't need or want the 'pip-pip-pip' indication by audio...
enableNoAudioDetection:false,
enableTalkWhileMuted:false,
disableAudioLevels: true,
)

            let config = {
              enableNoisyMicDetection:false,
              enableNoAudioDetection:false,
              enableTalkWhileMuted:false,
              disableAudioLevels: true,

              // whole room by creator?
              //startAudioOnly:true,
              startWithAudioMuted: true,
              // only this person
              startWithVideoMuted: true,
              enableCalendarIntegration: false,
              disableThirdPartyRequests: true,
              disableRecordAudioNotification: true,
              //testing:{
                //noAutoPlayVideo:true,
              //},
              //chromeExtensionBanner: {},
              disableInviteFunctions: true,
              disableRemoteMute: true,
            };

            let interfaceConfig = {
              DISPLAY_WELCOME_PAGE_CONTENT: false,
              MOBILE_APP_PROMO: false,


            };

            this.jitsi_api = new JitsiMeetExternalAPI('meet.jit.si', {
              parentNode: this.$refs['putithere'],
              roomName: this.settings.roomName,
              configOverwrite: config,
              interfaceConfigOverwrite: interfaceConfig,
            });

it's important I work around this in the very short term; any ideas?

Simon

Jasper-Ben · 2020-05-04T17:19:20Z

video muted; which could be related/

In my experience the issue described here only occurs when disabling audio on entering the room.
So changing startWithAudioMuted: true, to startWithAudioMuted: false, might be a short term workaround?

Other than that, I cannot really help as I am unfamiliar with the api.

btsimonh · 2020-05-06T05:31:54Z

something else; watch out for
The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
I think this prevented one of my jitsi clients from starting audio?

tomkel · 2020-05-27T05:32:17Z

I still have this bug in rel 4548. In a call with ~15 people

domrim · 2021-06-24T11:23:50Z

@jallamsetty1 we have the same issues as everyone else here. Is this fix allready present in jitsi/stable? or better: which commit fixed the issue?

loelkes · 2021-06-24T15:09:12Z

Hi Dominik ;)

@jallamsetty1 we have the same issues as everyone else here. Is this fix allready present in jitsi/stable? or better: which commit fixed the issue?

Check your JavaScript console logs on the clients facing the audio issues. If there are AudioContext errors than try enabling the pre-join page. If the browser enforces the requirement for an user gesture before accessing the AudioContext it seems there's no way around the pre-join page. It seems a bit random how strictly browser implement this.

Enabling the Pre-Join page solved an incredible amount of issues related to audio on all my setups.

franciscoescher · 2021-10-07T22:09:19Z

Also getting this error using the open service (https://meet.jit.si/), using chrome

midn1 · 2021-12-06T10:17:24Z

Still happens on meet.ji.si, and it is very difficult to keep people from Zoom when this sort of thing is common..

c0m1t · 2021-12-07T15:01:44Z

Using pre-join page and there shouldn't be a problem. It needs a gesture or webrtc session before playing it is how Google changed it ... not sure about FF though.

@damencho We have a prejoin page but sometimes on chrome browser on mobile we get this error:

 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
(anonymous) @ lib-jitsi-meet.min.js:1
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:10
(anonymous) @ lib-jitsi-meet.min.js:10
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:10
(anonymous) @ lib-jitsi-meet.min.js:10
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:10
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:17
(anonymous) @ lib-jitsi-meet.min.js:17
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:17
n @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1
lang/countries-fa.json?r=1638779169516:1 Failed to load resource: the server responded with a status of 404 ()
 [Deprecation] The ScriptProcessorNode is deprecated. Use AudioWorkletNode instead. (https://bit.ly/audio-worklet)
_initializeAudioContext @ lib-jitsi-meet.min.js:1
c @ lib-jitsi-meet.min.js:1
(anonymous) @ lib-jitsi-meet.min.js:1

When this happens other participants cannot hear the participant audio.

saghul · 2021-12-07T15:03:33Z

Folks, this issue is really old, please open a new one and provide as much info as you can. Thank you!

de1phi48 · 2023-02-12T11:39:58Z

Good day, we have a same problem. in a conference of 15 people, one or two people may not be able to hear the others, and the microphone stops working. We use own instanse Jitsi+Rocket.Chat

havaeng · 2024-01-18T17:47:12Z

Hello, just wanted to inform that I'm experiencing this right now. I can't hear 2 of the 7 participants (not counting myself). Everyone can hear me. Safari version 17.0 (19616.1.27.211.1)

saghul · 2024-01-18T18:18:11Z

@jallamsetty1 ^

jallamsetty1 · 2024-01-19T18:33:30Z

Hi @havaeng, can you please share more details? Is this happening on meet.jit.si or on your deployment? Were you able to hear those 2 users in the beginning and then stopped hearing them all of a sudden or did the issue exist from the moment those users unmuted themselves and started speaking? Will you be able to share the full browser console logs for the call when this issue reproduces?

isality · 2024-07-16T09:13:10Z

Same issue.

Firefox 128.0
Jitsi stable-9457

no sound and video in Firefox. Chrome works fine.

I got error messages in console:

2024-07-16T08:38:31.726Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>:  A potential problem is detected with the audio output for participant 63c60420, local audio levels: [null,null], remote audio levels: undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
2024-07-16T08:38:31.727Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>:  A potential problem is detected with the audio output for participant becfffa0, local audio levels: [null,null], remote audio levels: undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
2024-07-16T08:38:31.727Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>:  A potential problem is detected with the audio output for participant 3f6da3ec, local audio levels: [null,null], remote audio levels: undefined [Logger.js:155:26](webpack://JitsiMeetJS/node_modules/@jitsi/logger/lib/Logger.js)
2024-07-16T08:38:31.727Z [modules/statistics/AudioOutputProblemDetector.js] <526/_onLocalAudioLevelsReport/<>:  A potential problem is detected with the audio output for participant e3aee918, local audio levels: [null,null], remote audio levels: undefined

Could someone check that?

saghul · 2024-07-16T10:52:39Z

CAn you reproduce this consistently? Can you please share the full JS console logs?

isality · 2024-07-16T14:01:15Z

@saghul hi, full console log in attachment.

stepps to reproduce:

go to any rooms
no one hears what I say
I can't hear anyone
web camera does not work also

if im changed browser on google chrome, evrything works fine

console-export-2024-7-16_16-39-23.txt

saghul · 2024-07-16T14:19:14Z

The link seems to be broken.

isality · 2024-07-16T14:24:18Z

@saghul link fixed

jallamsetty1 · 2024-07-16T17:22:13Z

Can you please try with the latest stable? There were some breaking changes with Firefox and DTLS 1.3 that have been addressed recently in the JVB.

isality · 2024-07-17T07:20:57Z

yes, I can, but it will take a lot of time. The update process is very slow in my company.

jallamsetty1 · 2024-07-17T14:03:03Z

Can you reproduce the issue with older versions of Firefox? If not, then the DTLS change in latest FF is the likely culprit and updating the JVB is the only option then. JVB ICE never got established as per the browser console log so it does seem very likely that its the DTLS issue.

isality · 2024-07-17T15:48:04Z

Firefox 125 same. No sound / video. Tested on mac pro (m2) and ubuntu 22.04.

jallamsetty1 · 2024-07-17T16:27:05Z

Firefox 125 same. No sound / video. Tested on mac pro (m2) and ubuntu 22.04.

Are you able to reproduce this on meet.jit.si?

isality · 2024-07-17T16:33:27Z

meet.jit.si - works fine!

isality · 2024-07-18T10:20:16Z

@jallamsetty1 hi! whats version of jvb server and jitsi using meet.jit.si?

saghul · 2024-07-18T10:44:57Z

That deployment is always a bit ahead of our stable releases, but in your case using the latest stable release should do it.

isality · 2024-07-18T11:12:09Z

@saghul thank you. I think the update will solve my problem.

isality · 2024-07-22T15:23:31Z

after update on latest stable release - firefox works fine.

jonnius changed the title ~~Sometimes participants can't hear all other participants~~ Sometimes participants can't hear other participants Mar 18, 2020

damencho mentioned this issue Mar 20, 2020

Firefox - user is shown as muted #5181

Closed

damencho closed this as completed Mar 20, 2020

luixxiul added the performance Issue related to performance of the app or browser when running Jitsi Meet label May 24, 2020

jallamsetty1 closed this as completed Jun 10, 2021

opencoca mentioned this issue Jun 25, 2021

Stuck in an alternate universe. opencoca/lt2d_school#18

Closed

shevchukma mentioned this issue May 12, 2023

Hearing problems when the startAudioMuted option is enabled #13347

Closed

jallamsetty1 mentioned this issue Jul 22, 2024

Jitsi doesn't work in Firefox-based browsers #13839

Closed

tio-trom mentioned this issue Aug 5, 2024

update to 2.0.9646 YunoHost-Apps/jitsi_ynh#147

Merged

2 tasks

Sometimes participants can't hear other participants #5230

Sometimes participants can't hear other participants #5230

Comments

jonnius commented Mar 18, 2020 • edited Loading

Description

Current behavior

Expected Behavior

Possible Solution

Steps to reproduce

Environment details

rettichschnidi commented Mar 19, 2020

damencho commented Mar 19, 2020

rettichschnidi commented Mar 20, 2020 • edited Loading

damencho commented Mar 20, 2020

jonnius commented Mar 20, 2020

damencho commented Mar 20, 2020

Jasper-Ben commented Mar 23, 2020 • edited Loading

jonnius commented Mar 23, 2020

Jasper-Ben commented Mar 23, 2020 • edited Loading

jonnius commented Mar 23, 2020

Jasper-Ben commented Mar 23, 2020

jonnius commented Mar 24, 2020 • edited Loading

saghul commented Mar 24, 2020

Jasper-Ben commented Mar 24, 2020 • edited Loading

Jasper-Ben commented Mar 24, 2020 • edited Loading

Isolator70 commented Mar 24, 2020

Isolator70 commented Mar 25, 2020 • edited Loading

keinstein commented Apr 5, 2020

real-or-random commented Apr 5, 2020

thomaswucher commented Apr 28, 2020

Jasper-Ben commented Apr 28, 2020 • edited Loading

jonnius commented May 2, 2020

btsimonh commented May 4, 2020

Jasper-Ben commented May 4, 2020

btsimonh commented May 6, 2020

tomkel commented May 27, 2020 • edited Loading

domrim commented Jun 24, 2021

loelkes commented Jun 24, 2021

franciscoescher commented Oct 7, 2021

midn1 commented Dec 6, 2021

c0m1t commented Dec 7, 2021

saghul commented Dec 7, 2021

de1phi48 commented Feb 12, 2023

havaeng commented Jan 18, 2024

saghul commented Jan 18, 2024

jallamsetty1 commented Jan 19, 2024

isality commented Jul 16, 2024

saghul commented Jul 16, 2024

isality commented Jul 16, 2024 • edited Loading

saghul commented Jul 16, 2024

isality commented Jul 16, 2024

jallamsetty1 commented Jul 16, 2024

isality commented Jul 17, 2024

jallamsetty1 commented Jul 17, 2024 • edited Loading

isality commented Jul 17, 2024

jallamsetty1 commented Jul 17, 2024

isality commented Jul 17, 2024

isality commented Jul 18, 2024

saghul commented Jul 18, 2024

isality commented Jul 18, 2024

isality commented Jul 22, 2024

jonnius commented Mar 18, 2020 •

edited

Loading

rettichschnidi commented Mar 20, 2020 •

edited

Loading

Jasper-Ben commented Mar 23, 2020 •

edited

Loading

Jasper-Ben commented Mar 23, 2020 •

edited

Loading

jonnius commented Mar 24, 2020 •

edited

Loading

Jasper-Ben commented Mar 24, 2020 •

edited

Loading

Jasper-Ben commented Mar 24, 2020 •

edited

Loading

Isolator70 commented Mar 25, 2020 •

edited

Loading

Jasper-Ben commented Apr 28, 2020 •

edited

Loading

tomkel commented May 27, 2020 •

edited

Loading

isality commented Jul 16, 2024 •

edited

Loading

jallamsetty1 commented Jul 17, 2024 •

edited

Loading