-
Notifications
You must be signed in to change notification settings - Fork 13k
fix: VoIP widget mute action muting received audio instead of just microphone. #36229
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
Conversation
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: 0ee5d55 The changes in this PR will be included in the next version bump. This PR includes changesets to release 37 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #36229 +/- ##
========================================
Coverage 64.52% 64.53%
========================================
Files 3148 3148
Lines 104632 104632
Branches 19769 19802 +33
========================================
+ Hits 67519 67527 +8
+ Misses 34425 34418 -7
+ Partials 2688 2687 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Proposed changes (including videos or screenshots)
For some reason both
senderandreceivertracks were being muted simultaneously. The code was very similar to the "setHold" method, which does actually mute both users, as well as sends a message so that the peer client knows the call is on hold.In fact,
setMutewas also sending a "re-INVITE" for some reason. This is not necessary, as the peer client does not need to know if the other peer's microphone is muted or not. That information is only relevant for setting the call on hold.The fix removes this "re-invite" logic and simply mutes ONLY the sender tracks, disabling the mic, but keeping the received audio playing.
Issue(s)
VSTAB-26
Steps to test or reproduce
Tip: If testing locally with the same machine, you can mute the browser tab to figure out which user the audio is coming from.
Further comments