5 ms·
It's the 2Mb/s upload in my example that's the catch. That'll often be asymmetric at a 10:1 download:upload ration (or worse), so it's almost impossible to do
by donmcronald 3y ago
It's the 2Mb/s upload in my example that's the catch. That'll often be asymmetric at a 10:1 download:upload ration (or worse), so it's almost impossible to do any kind of traffic management to make it work well.
I'm talking about places that can't get an internet connection that can support the VOIP systems they're sold.
- BenjiWiebe 3y agoI hear you with the 2Mb/s upload, but that isn't a problem for VoIP in and of itself. What makes 2Mb/s upload an issue with VoIP is not having a good router (i.e. one with CAKE queuing support or something similar) and then getting hammered with buffer bloat making your latencies go to 1000+ ms because someone's iPhone decided to back something up (don't know why it never seems to be an issue with Androids). ^ The above is precisely my experience and is a large part of why my workplace hasn't moved to VoIP yet, despite needing the features.
- supertrope 3y ago2 Mbps is tight but can definitely support 0.1 Mb/s calls. The vendor needs to ensure the phones tag audio packets with EF priority and the router uses a strict priority queue. (Whenever a voice packet arrives it pauses handling non-voice traffic until the voice queue is clear. This ensures a voice packet is never delayed by more than 1500B / 2 Mbps = 6 ms). https://www.cisco.com/c/en/us/support/docs/voice/voice-quality/5125-delay-details.html#serializationdelay https://www.cisco.com/c/en/us/support/docs/voice/voice-quali...