Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some participants are lacking audio #9805

Closed
zabbal opened this issue Aug 25, 2021 · 17 comments
Closed

Some participants are lacking audio #9805

zabbal opened this issue Aug 25, 2021 · 17 comments
Labels
wontfix Issue won't be fixed

Comments

@zabbal
Copy link

zabbal commented Aug 25, 2021

Description:

While in jitsi meet conference I sometimes experience no audio from some participant. At the same time I can see their screen (when shared) and I can hear audio from other participants.
Is there a way to debug this sort of issues? Perhaps it's an issue others have hit already? Some odd NAT-related problem?

Steps to reproduce:

It seems to be specific to some participants but not the others. Note: I do not hear the audio from participant X but I can hear audio from participant Y and Y can hear X's audio.

Expected behavior:

Audio always works.

Actual behavior:

Audio sometimes works.

Server information:

Ubuntu 21.04

Client information:

Ubuntu 21.04
Falkon 3.1.0

Additional information:

Not sure how this can be tracked down - any ideas would be appreciated.

@gpatel-fr
Copy link

Sorry but in the template you have missed this important notice:

General questions regarding usage, installation, etc. should be posted at https://community.jitsi.org. They will be closed if posted here

general questions are something along the lines of 'not sure on how to debug the issue ?'. You also ask if others have your issue, while the template states explicitly that it is your responsability.
.
So be kind enough to close this issue and post your question where it belongs, on community.jitsi.org.

@zabbal
Copy link
Author

zabbal commented Aug 29, 2021

Lack of audio for some participants of the call is not "general question" - that's a bug in jitsi-meet which needs to be fixed.

@gpatel-fr
Copy link

if you say so... The point is that you did not provide nearly enough information for a developer to operate on it.

@zabbal
Copy link
Author

zabbal commented Aug 30, 2021

Yeah, that's how some bugs are. And that's why we have public issue tracker - so others can contribute and together we can resolve the bugs. Please refrain from random comments unless they actually provide useful information towards that goal.

@damencho
Copy link
Member

Do you experience it on meet.jit.si? If not which version is that you self host?

@zabbal
Copy link
Author

zabbal commented Aug 31, 2021

I've seen this happening twice on self-hosted instances. I don't know version in first case (happened couple of months ago), in more recent case it was 2.0.6173-1 - installed on latest Ubuntu via jitsi-provided packages.

The configs are available at https://github.com/emacs-berlin/emacs-berlin.org/blob/gh-pages/ansible/jitsi.yml

I suspect it might be smth TURN/STUN related but unsure how we can troubleshoot this. Is there some particular log setup or settings we could try?

@damencho
Copy link
Member

Do you have pre-join screen enabled? If not, try that.

Gathering logs from the client that is not hearing some and the id of the participant that is not heard and sharing it with us is next step.

@zabbal
Copy link
Author

zabbal commented Aug 31, 2021

Yepp, pre-screen is enabled. The audio is broken one-way: I can hear some participants and the participants I can't hear have no problem hearing me.

@damencho
Copy link
Member

So when this happens you can note the id of the participant you don't hear and save your js console logs and send it here. Thank you.

@Rintan
Copy link

Rintan commented Sep 13, 2021

I have the same issue.

Here is my javascript console logs.

Logger.js:154 2021-09-13T12:38:42.290Z [modules/xmpp/strophe.emuc.js] <u.createRoom>:  You are already in the room!
o @ Logger.js:154
Logger.js:154 2021-09-13T12:38:42.292Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: You are already in the room! Script: null Line: null Column: null StackTrace:  Error: You are already in the room!
    at u.createRoom (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:145923)
    at P.createRoom (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:133497)
    at ue._init (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:41493)
    at new ue (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:39436)
    at c.initJitsiConference (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:37445)
    at Object._createRoom (https://jitsi.example.com/libs/app.bundle.min.js?v=5307:193:11530)
    at Object.startConference (https://jitsi.example.com/libs/app.bundle.min.js?v=5307:193:6506)
    at Object.prejoinStart (https://jitsi.example.com/libs/app.bundle.min.js?v=5307:193:8086)
o @ Logger.js:154
strophe.emuc.js:62 Uncaught (in promise) Error: You are already in the room!
    at u.createRoom (strophe.emuc.js:62)
    at P.createRoom (xmpp.js:651)
    at ue._init (JitsiConference.js:342)
    at new ue (JitsiConference.js:133)
    at c.initJitsiConference (JitsiConnection.js:113)
    at Object._createRoom (conference.js:1326)
    at Object.startConference (conference.js:737)
    at Object.prejoinStart (conference.js:859)
Logger.js:154 2021-09-13T12:38:43.145Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: Strophe: TypeError: Cannot read properties of undefined (reading 'isFocus')
    at ue.onIncomingCall (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:62275)
    at a.emit (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:119812)
    at E.onJingle (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:211488)
    at w.Handler.run (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:27486)
    at https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35924
    at Object.forEachChild (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:19148)
    at w.Connection._dataRecv (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35773)
    at O.Bosh._onRequestStateChange (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:55758) Script: null Line: null Column: null StackTrace:  Error: Strophe: TypeError: Cannot read properties of undefined (reading 'isFocus')
    at ue.onIncomingCall (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:62275)
    at a.emit (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:119812)
    at E.onJingle (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:211488)
    at w.Handler.run (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:27486)
    at https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35924
    at Object.forEachChild (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:19148)
    at w.Connection._dataRecv (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35773)
    at O.Bosh._onRequestStateChange (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:55758)
    at Object.r.Strophe.log (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:17:16531)
    at Object.fatal (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:24419)
    at Object._handleError (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:23810)
    at w.Handler.run (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:27514)
    at https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35924
    at Object.forEachChild (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:19148)
    at w.Connection._dataRecv (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35773)
    at O.Bosh._onRequestStateChange (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:55758)
o @ Logger.js:154
Logger.js:154 2021-09-13T12:38:43.145Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>:  Strophe: TypeError: Cannot read properties of undefined (reading 'isFocus')
    at ue.onIncomingCall (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:62275)
    at a.emit (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:119812)
    at E.onJingle (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:10:211488)
    at w.Handler.run (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:27486)
    at https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35924
    at Object.forEachChild (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:19148)
    at w.Connection._dataRecv (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35773)
    at O.Bosh._onRequestStateChange (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:55758)
o @ Logger.js:154
Logger.js:154 2021-09-13T12:38:43.145Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: Strophe: error: Cannot read properties of undefined (reading 'isFocus') Script: null Line: null Column: null StackTrace:  Error: Strophe: error: Cannot read properties of undefined (reading 'isFocus')
    at Object.r.Strophe.log (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:17:16531)
    at Object.fatal (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:24419)
    at Object._handleError (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:24029)
    at w.Handler.run (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:27514)
    at https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35924
    at Object.forEachChild (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:19148)
    at w.Connection._dataRecv (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:35773)
    at O.Bosh._onRequestStateChange (https://jitsi.example.com/libs/lib-jitsi-meet.min.js?v=5307:1:55758)
o @ Logger.js:154
Logger.js:154 2021-09-13T12:38:43.145Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>:  Strophe: error: Cannot read properties of undefined (reading 'isFocus')
o @ Logger.js:154
[modules/connectivity/ParticipantConnectionStatus.js] <g.onTrackRtcMuted>:  No participant for id: 6d5cc1ee

@Rintan
Copy link

Rintan commented Sep 13, 2021

I also found the same issue on lib-jitsi-meet.

jitsi/lib-jitsi-meet#1693

@Rintan
Copy link

Rintan commented Oct 6, 2021

Pre-requirements

  • Pre-join (pre-meeting) page enabled
  • Using authentications (I've tested on jwt token authentications)
  • Jitsi Meet 2.0.6173 or newer

Steps to reproduce

Some participants can't hear others audio though they don't muted.

Server information

Ubuntu 20.04

@stale
Copy link

stale bot commented Jan 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Issue won't be fixed label Jan 8, 2022
@stale stale bot closed this as completed Apr 30, 2022
@zabbal
Copy link
Author

zabbal commented Aug 8, 2022

I've noticed that this can be "fixed" by closing the browser tab and re-joining the conference in a new tab. So it's not some generic browser or network connectivity issue - that's smth jitsi-specific.

@zabbal
Copy link
Author

zabbal commented Aug 8, 2022

Also, can we re-open this - the issue still affects multiple users without proper fix. Keep closing and opening jitsi is also hardly acceptable workaround.

@3ynm
Copy link

3ynm commented Nov 25, 2022

Same thing happened me during my first class on a course. 3 people out of 13 had problems hearing some other people (but not every other people). I've lost some students because of it :(

@damencho
Copy link
Member

Please do not use old threads. Open a new topic in the forum explaining the problem. What deployment do you use? Is it meet.jit.si? If you are hosting your own maybe upload the config.js and what versions of the packages do you use? What browsers and versions were used by those that do not hear? Have you managed to download some client logs (browser js console logs)?

@jitsi jitsi locked and limited conversation to collaborators Nov 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
wontfix Issue won't be fixed
Projects
None yet
Development

No branches or pull requests

5 participants