4 ms·

I've helped plenty of clients where QoS changed their VoIP phones from "not working" to "working." You can push my Windows Update example to 6pm -- I still don

I've helped plenty of clients where QoS changed their VoIP phones from "not working" to "working." You can push my Windows Update example to 6pm -- I still don't care at all how it runs. I'd tell my router to mark it as the least time-sensitive of any of my network connections.

AnthonyMouse 13y ago
> I've helped plenty of clients where QoS changed their VoIP phones from "not working" to "working." Because QoS on a LAN is a different animal. A LAN will have multiple machines that each have a 100Mbps or faster connection to a shared router with a 100Mbps or slower link to the rest of the Internet. That means one person downloading anything will saturate the entire Internet connection. ISPs have the opposite topology: A bunch of users with e.g. 50Mbps connections that come together to share a multi-Gbps uplink. Regularly saturating the uplink in that context is Bad. It means customers aren't getting the speeds you sold them. There is also a difference between QoS and fairness. If you're using VOIP and I'm downloading something, the ISP should be dropping my packets before yours when we're on the same plan, but because of the quantity of traffic rather than the type. That pretty much exempts VoIP from being dropped, without doing any kind of DPI or traffic classification, based simply on how relatively little bandwidth it requires.