Network & Call Check
Confirm basic web connectivity and application-level round trip before checking camera, microphone, and speakers for a call.
A call can fail because the internet path is unstable or because camera/microphone/audio routing is wrong. Test network and media independently before treating them as one problem.
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.
Check whether another device on the same network has the same call problem.
Why it matters: This separates one-device configuration from a wider network/service issue.If possible, compare Ethernet or a stronger Wi-Fi location without changing other settings.
Why it matters: Improvement points toward the local wireless path.Use the meeting service's official status/test-call feature when available.
Why it matters: A service incident can mimic local network failure.Conditions that deserve caution
- Work/school network policy blocks the service and you are not authorized to alter it.
- Router/modem power hardware is damaged or overheating.
How to use the evidence
If general connectivity is stable and DeviceOK media tests pass, prioritize the call service/app. If several devices show the same instability, prioritize network/router/ISP layers.