247993 2022-11-16 13:52:14 -0800 Incoming and Outgoing audio does not recover automatically and "Microphone" stays in muted state after the PSTN call if User receives PSTN call in the middle of WebRTC call 2025-05-25 23:32:18 -0700 1 1 1 Unclassified WebKit WebRTC Safari 16 iPhone / iPad iOS 16 RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=247994 https://bugs.webkit.org/show_bug.cgi?id=246331 InRadar P2 Normal --- 1 madara.freimane webkit-unassigned webkit-bug-importer youennf oldest_to_newest 1912953 0 madara.freimane 2022-11-16 13:52:14 -0800 Summary: Outgoing audio does not recover automatically and "Microphone" stays in muted state after the PSTN call if User receives PSTN call in the middle of WebRTC call Tested devices: Bug is reproducible on: * iPhone 14 (iOS 16.2 Beta 3, build: 20C5049e) and Safari * iPhone 11 Pro Max (iOS 16.2 Beta 3, build: 20C5049e) and Safari * iPhone 13 (iOS 15.7.1) and Safari Scenario: Precondition: User is in active WebRTC call Steps: 1. User receives PSTN call 2. User accepts PSTN call 3. User ends PSTN call Actual result: Outgoing audio does not recover automatically and "Microphone" stays in muted state after the PSTN call if User receives PSTN call in the middle of WebRTC call (Sometimes User loses incoming and outgoing audio until re-enables "Microphone") Expected result: Outgoing audio recovers automatically and "Microphone" changes muted state to unmuted after the PSTN call if User receives PSTN call in the middle of WebRTC call Reproducibility: 40% Additional information: -Sysdiagnostics file added (bug reproduced at 23:15, 16.11.2022, EET time zone): https://drive.google.com/file/d/10Isd94hfJzqvTc6N1KIB0q-mrfKkke39/view?usp=share_link 1914368 1 webkit-bug-importer 2022-11-23 13:53:16 -0800 <rdar://problem/102633531> 1948726 2 youennf 2023-04-14 00:22:08 -0700 *** Bug 240651 has been marked as a duplicate of this bug. *** 1948728 3 youennf 2023-04-14 00:22:21 -0700 *** Bug 247994 has been marked as a duplicate of this bug. *** 2023709 4 madara.freimane 2024-03-25 03:43:03 -0700 This issue is no longer relevant. Seems has been fixed with iOS 16.4. Thank you very much!