-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Third person joining causes loss of audio for first two participants #14195
Comments
We are experiencing the same issue. |
Can you provide js console logs from the browser for such a session? |
Please try |
Disabling P2P would of course cause the call to stay on the JVB. |
Where did this flag get input? Is it a requirement for all participants?
…On Fri, 12 Jan 2024, 07:34 slesru, ***@***.***> wrote:
Please try
p2pTestMode: true
btw, looks like firefox has no such problem
—
Reply to this email directly, view it on GitHub
<#14195 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMDBJD7LN4H6ZQVOLQV66N3YODRSBAVCNFSM6AAAAABBKUKO5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGU3DQOBSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
No, it shouldn't be required. It looks like there might be a bug in switching to P2P. What Firefox version are you using? |
At the time of testing we had the same problem using chrome 120 and no such problem using firefox 120. |
It is in server config. In section |
We’re not using a local version but the main hosted system so I guessing won’t be able to do this.
From: slesru ***@***.***>
Sent: 12 January 2024 09:18
To: jitsi/jitsi-meet ***@***.***>
Cc: AlistairFielden ***@***.***>; Author ***@***.***>
Subject: Re: [jitsi/jitsi-meet] Third person joining causes loss of audio for first two participants (Issue #14195)
Where did this flag get input? Is it a requirement for all participants?
It is in server config.
Probably in
/etc/jitsi/meet/yourserver-config.js
In
testing: {
section
—
Reply to this email directly, view it on GitHub <#14195 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMDBJD4XAA3FNCTC6NMBVPDYOD5SXAVCNFSM6AAAAABBKUKO5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYG4YTOOBQGE> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AMDBJD3TRH5H5TZAAIYVYTTYOD5SXA5CNFSM6AAAAABBKUKO5WWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTQSOF6S.gif> Message ID: ***@***.*** ***@***.***> >
|
I guess you can do this in url https://community.jitsi.org/t/how-to-how-to-customize-meeting-options/74665 never tried this though |
Is this going to be fixed? @saghul |
We are not aware of such problem in the latest version running on meet.jit.si. Are you testing there or your own server? In case of the latter, please provide the versions of the software you installed. |
@jallamsetty1 does this ring any bell? |
We're using the latest chrome version on Ubuntu lts. |
We are not aware of any such issues with the last stable release. Can you please provide logs for all 3 participants? |
Whilst using the meet.jit.si website since using the
#config.p2pTestMode=true switch we've not had a recurrence of the audio
dropout issues
…On Wed, 6 Mar 2024 at 16:08, Jaya Allamsetty ***@***.***> wrote:
We are not aware of any such issues with the last stable release. Can you
please provide logs for all 3 participants?
—
Reply to this email directly, view it on GitHub
<#14195 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMDBJD7OMVX3DXXY42BCH4DYW45QVAVCNFSM6AAAAABBKUKO5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRGIZDCNRWHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Regards,
Alistair Fielden
10 Caister Close, Seaham, County Durham, SR7 7WP
0753 800 1013
***@***.***
|
Fresh installation and I can also confirm the issue. |
Can you pls please provide logs from all the 3 users? |
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. |
fresh installation - same problem here |
Please open a new issue and provide logs for all participants and the backend services. |
@Theog75 found that the server is too far away (another continent in my case) or does not have powerful configuration that will produce the issues. |
I have faced same problem (Third person joining causes loss of audio for first two participants in jitsi). |
Using the general meet.jit.si web site since adding the suggested switch below I have not had any further issues
meet.jit.si/<MeetingName>#config.p2pTestMode=true
…--
Regards,
Alistair Fielden
From: vinod325 ***@***.***>
Sent: 07 August 2024 09:00
To: jitsi/jitsi-meet ***@***.***>
Cc: AlistairFielden ***@***.***>; Author ***@***.***>
Subject: Re: [jitsi/jitsi-meet] Third person joining causes loss of audio for first two participants (Issue #14195)
I have faced same problem (Third person joining causes loss of audio for first two participants in jitsi).
Now I have resolve this issue, firstly follow the Jitsi document(https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart/) for jitsi installation in ubuntu server.
If you setup and configure your firewall in ufw, please also add 10000 port with custom UDP in ec2 security group then Jitsi meet work fine
—
Reply to this email directly, view it on GitHub <#14195 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMDBJD2U5PD7D3ZK2U4YCV3ZQHHXVAVCNFSM6AAAAABBKUKO5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZSHA2TQMRWGA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AMDBJD7KD7C5JCBXUNPMZ3LZQHHXVA5CNFSM6AAAAABBKUKO5WWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUHPEIJI.gif> Message ID: ***@***.*** ***@***.***> >
|
Description:
After the start of a session via meet.jit.si website first two users in and audio and video are fine. When a third person joins the third persons audio is all that can be heard. If one of the original two drops out and comes back in then it switches so that the their audio is all that can be heard. Muting and un-muting users audio has no effect.
Switching from Chrome to other browsers seemed to cure the issue.
Issue started occurring in December 2023.
Steps to reproduce:
As description
Expected behavior:
Audio from all participants is heard on all sessions
Actual behavior:
Audio from last joining user is all that can be heard
Server information:
Client information:
Additional information:
The text was updated successfully, but these errors were encountered: