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.

Sign up for GitHub

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

Jump to bottom

Found an issue when the user starts screen sharing in the mobile app and stops and tries to open his camera, the user in the browser cant see his video in p2p #11010

Closed
zaki-vempower opened this issue Feb 23, 2022 · 3 comments · Fixed by jitsi/lib-jitsi-meet#1944
Closed

Found an issue when the user starts screen sharing in the mobile app and stops and tries to open his camera, the user in the browser cant see his video in p2p #11010

zaki-vempower opened this issue Feb 23, 2022 · 3 comments · Fixed by jitsi/lib-jitsi-meet#1944

Comments

@zaki-vempower
Copy link

zaki-vempower commented Feb 23, 2022 •
edited
Loading

Description:

Steps to reproduce:

  1. Open android/ios app and join the conference p2p
  2. start screensharing
  3. stop screen sharing
  4. Try to open your video cam
  5. The user in the browser cant see the video of the user in the app

Expected behavior:

Actual behavior:

when the user shares screen in android or ios and tries to open his camera the user in the web cant see his video in p2p
The error => addRemoteStream failed: DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote offer sdp: Media section has more than one track specified with a=ssrc lines which is not supported with Unified Plan.

Screenshot from 2022-02-23 15-30-12

Server information:

  • Jitsi Meet version: main website idk what version its running on.
  • Operating System:Ubuntu 20.04

Client information:

  • Browser / app version:
  • Operating System: Chrome

Additional information:

Thanks ,
@zaki-vempower zaki-vempower changed the title Found an issue when the user starts screen sharing in the mobile app and stops and tries to open his camera, the user in the browser cant see his video Found an issue when the user starts screen sharing in the mobile app and stops and tries to open his camera, the user in the browser cant see his video in p2p Feb 23, 2022
@saghul
Copy link
Member

saghul commented Feb 23, 2022

Thanks for the report! @jallamsetty1 this sounds very close to what I told you yesterday. If you can take a look that would be great I also plan to do so tomorrow.

jallamsetty1 added a commit to jallamsetty1/lib-jitsi-meet that referenced this issue Mar 1, 2022
@jallamsetty1
fix(JingleSessionPC) Remove the ssrc lines in remote desc sdp on sour…
adc7c40 
…ce removal.

In P2P and unified mode, Chrome does not render the media if an SSRC is removed and the same one is added back (happens when the sender is camera muted->starts SS->stops SS->turns camera on). That is why SSRC was not being removed. However, mobile endpoints that are running in plan-b generate a new SSRC when the client switches between camera and screenshare. This will cause issues on a p2p receiver that is running in unified mode. Fixes jitsi/jitsi-meet#11010.
@jallamsetty1 jallamsetty1 mentioned this issue Mar 1, 2022
Merged
jallamsetty1 added a commit to jitsi/lib-jitsi-meet that referenced this issue Mar 1, 2022
@jallamsetty1
fix(JingleSessionPC) Remove the ssrc lines in remote desc sdp on sour…
d91581a 
…ce removal.

In P2P and unified mode, Chrome does not render the media if an SSRC is removed and the same one is added back (happens when the sender is camera muted->starts SS->stops SS->turns camera on). That is why SSRC was not being removed. However, mobile endpoints that are running in plan-b generate a new SSRC when the client switches between camera and screenshare. This will cause issues on a p2p receiver that is running in unified mode. Fixes jitsi/jitsi-meet#11010.
@jilson-johnson
Copy link

am having same issue

@saghul
Copy link
Member

saghul commented May 6, 2024

While it might manifest in the same way, it's unlikely to be the same. Please open a new issue and gather logs on both ends of the call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@saghul @zaki-vempower @jilson-johnson