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

fix(meetings): webrtc dumps are sometimes empty when users join a meeting via lobby #3836

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

marcin-bazyl
Copy link
Collaborator

COMPLETES #SPARK-562381

This pull request addresses

If a user joins a meeting and ends up in the lobby and later gets admitted to the meeting, it can take up to 30s before we send webrtc dump data after user is admitted to the meeting. If user has any issues, they often close the tab before we send webrtc dump data.

by making the following changes

Sending webrtc dump data sooner after being admitted. The data is collected every 5s, so it should be good enough if we just send the first batch of data we have after being admitted.

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios where tested

unit tests, manual test run with the web app

I certified that

  • I have read and followed contributing guidelines

  • I discussed changes with code owners prior to submitting this pull request

  • I have not skipped any automated checks

  • All existing and new tests passed

  • I have updated the documentation accordingly


Make sure to have followed the contributing guidelines before submitting.

@marcin-bazyl marcin-bazyl requested review from a team as code owners September 16, 2024 11:22
@@ -192,15 +190,13 @@ Media.createMediaConnection = (
config.bundlePolicy = bundlePolicy;
}

const rtcMetrics = new RtcMetrics(webex, meetingId, correlationId);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to move this to Meeting.createMediaConnection() so that I could store the reference to RtcMetricsas a private field of theMeeting. This way we can call this.rtcMetrics.sendNextMetrics()` when we are admitted into the meeting.

@marcin-bazyl marcin-bazyl added the validated If the pull request is validated for automation. label Sep 16, 2024
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-3836.d3m3l2kee0btzx.amplifyapp.com

Copy link
Contributor

@jor-row jor-row left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good to me, have tested locally with the scenario outlined in the PR description and it's working as expected

Copy link
Contributor

@Shreyas281299 Shreyas281299 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@marcin-bazyl marcin-bazyl merged commit 9bb81a2 into webex:next Sep 16, 2024
20 of 21 checks passed
pagour98 pushed a commit to pagour98/webex-js-sdk that referenced this pull request Sep 27, 2024
pagour98 pushed a commit to pagour98/webex-js-sdk that referenced this pull request Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
validated If the pull request is validated for automation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants