Call problems repeat. A small number of causes produce the same few symptoms, and the step that clears each one is usually short. Some of the work is already done for you while the call runs: the meeting shows what is affecting the call and the step worth trying next, and device controls sit inside the meeting, so switching a microphone or a camera does not mean leaving.
Find your symptom
Match what you are seeing to the first column and read across. Two of these need more than one step, and they are worked through in order after the table.
When unmuting does nothing
The microphone is being held somewhere between the hardware and the meeting, and you work back along that path. Take these in order and stop as soon as your voice arrives.
When the network filters meeting traffic
Offices, schools, hotels and guest wifi commonly restrict what is allowed out, and meeting traffic can be caught by those rules. Nothing you change on your own device will move it, so the point of these steps is to rule the network in or out and then take it to the person who runs it.
For a call that repeats, rule this one out once and write down the answer. A network rule rarely changes between one week and the next.
Before a call that matters
- Confirm camera and microphone access at both the browser and the system level while you still have time to change it.
- Prefer a wired connection or a strong wifi spot, and pick the room before the call starts.
- Ask the household or the office to keep heavy internet use down for the length of the call.
- Keep a short checklist where your team joins from, so the same steps get tried every time.
If your team hits the same symptom week after week, the fix is usually one level up from the call: a better wifi spot in the building, or a short conversation with whoever runs the network there.
- calls
- troubleshooting
- reliability