No Microphone in a Web Call on VPN? Separate Access and Network

Review site and system access separately

Chrome help recommends checking mute, site microphone access and system input controls. Site access is under privacy and site settings; managed browsers may require an administrator. There is no need to grant microphone access to every site.

Verify local input first

1. Check headset hardware mute and the call mute button, noting the selected input device.
2. Review microphone permission only for the trusted call site and follow system prompts for browser-level access.
3. Use the call input indicator or test and choose the intended headset or built-in microphone; speaker output does not verify input.
4. Once local input works, use a non-sensitive test with the same device and destination to compare VPN states without repeated route changes.
5. If there is still no input, contact device or call-app support first. If input works but transmission breaks, record times and network conditions for connection checks.

Feedback does not need meeting content

Share browser version, input device, permission state and whether input is detected. Do not upload meeting recordings, participant lists or access tokens. This guide makes no claim about Yunbao call-platform compatibility or measured latency.