For WiFi, the biggest issue is that if two devices transmit at the same time, they’ll interfere (“collide”) and both packets will get dropped and need to be retransmitted. Unlike phone networks, on WiFi there’s basically no coordination, so this interference is random and increases birthday-problem style as the network has more devices connected or has more traffic. There’s an exponential random backoff protocol to prevent infinite interference, but exponential backoff means exponentially increasing latency.
You can also get interference from devices connected to other WiFi networks on same channel (so just being in a busy part of town or an apartment building can add significant interference).
WiFi’s base speed is also limited to the slowest device on the channel, which has to do with the oldest supported protocol version, hardware, and distance. On a public network, you have a fairly high probability that at least one device is old and/or really far from the router, which drops the speed for everyone and makes the interference problem worse (since slower speed means each packet takes longer to send and therefore has more time when interference can disrupt it).
There’s a lot of stuff that interacts, so it’s possible to have 15 (or even more) people on calls on the same WiFi network, but you’d need:
A router fast enough that most of the theoretical bandwidth isn’t being used (unused bandwidth = lower chance of interference).
Everyone to be close enough to the router.
Everyone to be on reasonably modern devices.
Spaces that really care about this will use a bunch of high speed short-range access points (wired together) coupled with software to drop slow devices. It’s common-ish at conference centers, but not coffee shops, and even then they’re usually targeting acceptable latency/bandwidth for web browsing, not calls.
But yeah, in some cases a voice call on WiFi will work fine even with some other people on the network, but I wouldn’t trust all of the necessary stars to align consistently on a public network.
For WiFi, the biggest issue is that if two devices transmit at the same time, they’ll interfere (“collide”) and both packets will get dropped and need to be retransmitted. Unlike phone networks, on WiFi there’s basically no coordination, so this interference is random and increases birthday-problem style as the network has more devices connected or has more traffic. There’s an exponential random backoff protocol to prevent infinite interference, but exponential backoff means exponentially increasing latency.
You can also get interference from devices connected to other WiFi networks on same channel (so just being in a busy part of town or an apartment building can add significant interference).
WiFi’s base speed is also limited to the slowest device on the channel, which has to do with the oldest supported protocol version, hardware, and distance. On a public network, you have a fairly high probability that at least one device is old and/or really far from the router, which drops the speed for everyone and makes the interference problem worse (since slower speed means each packet takes longer to send and therefore has more time when interference can disrupt it).
There’s a lot of stuff that interacts, so it’s possible to have 15 (or even more) people on calls on the same WiFi network, but you’d need:
A router fast enough that most of the theoretical bandwidth isn’t being used (unused bandwidth = lower chance of interference).
Everyone to be close enough to the router.
Everyone to be on reasonably modern devices.
Spaces that really care about this will use a bunch of high speed short-range access points (wired together) coupled with software to drop slow devices. It’s common-ish at conference centers, but not coffee shops, and even then they’re usually targeting acceptable latency/bandwidth for web browsing, not calls.
But yeah, in some cases a voice call on WiFi will work fine even with some other people on the network, but I wouldn’t trust all of the necessary stars to align consistently on a public network.