Meeting Ready Check
Check camera, microphone, speakers, and browser access before a Zoom, Teams, Meet, Discord, or browser call.
A reliable call depends on four separate paths: network, camera, microphone and output audio. Passing DeviceOK narrows hardware failure; the meeting app still has its own device-selection and permission layer.
Run the browser-visible checks, then record the physical/native checks below. Progress stays in this browser unless you deliberately copy the fragment share link.
Browser-visible checks
Physical & native checks
These close the blind spots a website cannot inspect.
Open the real meeting app and confirm the same camera, microphone and speaker/headset are selected.
Why it matters: Apps can silently keep an old or virtual device selected.Check headset mute switches, laptop privacy controls and the app mute state.
Why it matters: A hardware mute can remain invisible to app-level troubleshooting.Join a short test call if the service offers one and observe stability, not only raw throughput.
Why it matters: Latency/jitter and enterprise policy can affect calls even when browsing works.Conditions that deserve caution
- Camera/microphone is blocked by organization policy that you are not authorized to change.
- Audio equipment produces abnormal heat or electrical noise.
How to use the evidence
If DeviceOK receives camera/mic/audio correctly but only one meeting app fails, fix the app/permission/routing layer before drivers or replacement.