[Webkit-unassigned] [Bug 204682] New: PeerConnection: Remote audio is muted if user receives phone call (even if phone call dismissed)
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Nov 28 07:34:12 PST 2019
https://bugs.webkit.org/show_bug.cgi?id=204682
Bug ID: 204682
Summary: PeerConnection: Remote audio is muted if user receives
phone call (even if phone call dismissed)
Product: WebKit
Version: Safari 13
Hardware: iPhone / iPad
OS: iOS 13
Status: NEW
Severity: Normal
Priority: P2
Component: WebRTC
Assignee: webkit-unassigned at lists.webkit.org
Reporter: daginge at confrere.com
CC: youennf at gmail.com
Summary:
If a user is in a WebRTC call and receives an incoming phone call, dismisses it, and comes back to Safari, the remote audio is muted.
Steps to reproduce:
1. Go to https://webrtc.github.io/samples/src/content/peerconnection/pc1/ on an iPhone running iOS 13.2.3
2. Start a peer connection
3. Verify that you hear the other side
4. Receive incoming phone call and dismiss it
5. Observe that you are taken back to Safari, and that the remote audio is now gone.
6. Hang up the call
7. Click "Call" again
8. Observe that you can now hear the other side again
Expected behaviour:
The video call is muted while the phone call is in progress, but that audio is resumed once the phone call has been ended/dismissed.
Actual behaviour:
The video call remote end is muted until the peer connection is restarted (does not seem like iceRestart does anything, has to be a new peer connection, possibly just a new video element).
Impact:
All sites using WebRTC on Safari for iOS, where the user might get a call in the middle of the video call.
Workaround:
Seems like restarting the peer connection or refreshing the page helps. You can somewhat detect this issue by doing audio analysis using WebAudio to check the output data of the remote stream. This appears to be 0. I have found no other workaround as of yet, but suspect killing the video DOM element and adding a new one should fix things.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191128/741c3600/attachment.htm>
More information about the webkit-unassigned
mailing list