Indeed, but in this case I'm dealing with a private network that doesn't have so much surplus as to guarantee no contention. C. -----Original Message----- From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu] Sent: Monday, February 10, 2003 1:23 PM To: Charles Youse Cc: Bill Woodcock; nanog@nanog.org Subject: Re: VoIP QOS best practices On Mon, 10 Feb 2003 13:02:39 EST, Charles Youse <cyouse@register.com> said:
That doesn't seem to make a lot of sense - is it that QoS doesn't work as advertised?
Qos is designed for dealing with "who gets preference when there's a bandwidth shortage". Most places are having a bandwidth glut at the moment, so the VoIP traffic gets through just fine and QoS isn't able to provide much measurable improvement.
> Indeed, but in this case I'm dealing with a private network that doesn't > have so much surplus as to guarantee no contention. You don't need a guarantee of no contention, you just have to be able to live with your web browser being slow if there isn't enough bandwidth to support both your phone call and your simultaneous web browsing. But the voice only uses about 9kbps per call, worst case, so you've got to have a _lot_ of simultaneous calls before it has a noticable effect on the rest of your traffic. -Bill
participants (2)
-
Bill Woodcock -
Charles Youse