Live audio and video make a demand that most software does not: sound and motion have to appear in sequence and almost as they happen. A brief interruption is heard as a stutter or seen as a face held still mid-word. The connection underneath a call does not cooperate with that. Capacity changes through the hour, and it changes hardest for people who move around, such as a phone crossing between towers or a laptop carried from one end of a building to the other.
What the call watches, and what it does about it
While a session runs, the call keeps a reading of how much of what is sent is getting through and whether it arrives at an even pace. The reading belongs to each connection separately, since a person on hotel wifi and a person on an office line are not in the same conditions and should not be treated as though they were. Every adjustment described below follows from that reading and happens without anyone pressing anything.
When less capacity is available, the call sends less. Video gives way first, so the picture loses sharpness or a little smoothness. Audio is the last thing to be reduced, because audio is the part the conversation depends on.
From a participant's seat this looks like a slightly worse image for a while, with the talking uninterrupted. When capacity comes back the picture climbs again on its own, and nobody has to reconnect to get it.
A short gap does not end the session
A phone entering a tunnel, a laptop moving between access points, a home line dropping for a moment: media stops arriving. The session is not torn down at the first gap. It is held open while the connection is re-established, and the participant carries on in the same meeting instead of landing back on a join screen and asking to be let in again. An outage that runs on long enough does close a session, but the brief gaps that make up most real interruptions do not.
The states a participant passes through
Who gets connected at all
Membership of a room is decided before any media flows. Someone asking to join waits at the door until a host admits them, and accounts themselves are provisioned after review. Holding an address does not put a person in a session. The participant list stays a list of people your organization approved.
The adapting and the recovering are not happening somewhere else. The audio and video of a meeting stay on systems your team already administers, and so does whatever a session leaves behind.
That order matters when you are reading a quality complaint. A participant who never got in has a different problem from one whose picture went soft, and the two get reported in the same sentence.
Judging this for your own networks
These behaviours are easier to watch than to read about. A reviewed demo puts a live session in front of you, and the useful thing to bring along is a description of the connections your own people join from, including the ones that give trouble.
- calls
- reliability
- self-hosted