That doesn't seem to make a lot of sense - is it that QoS doesn't work as advertised? As someone who is looking to deploy VoIP in the near future this is of particular interest. C. -----Original Message----- From: Bill Woodcock [mailto:woody@pch.net] Sent: Monday, February 10, 2003 12:48 PM To: nanog@nanog.org Subject: Re: VoIP QOS best practices > > Looking for some links to case studies or other documentation which > > describe implementing VoIP between sites which do not have point to > > point links. From what I understand, you can't enforce end-to-end QoS > > on a public network, nor over tunnels. I'm wondering if my basic > > understanding of this is flawed and in the case that it's not, how is > > this dealt with if the ISPs of said sites don't have any QoS policies? QoS is completely unnecessary for VoIP. Doesn't appear to make a bit of difference. Any relationship between the two is just FUD from people who've never used VoIP. -Bill
> That doesn't seem to make a lot of sense - is it that QoS doesn't work as advertised? That's generally true as well. But why would you need it? What's the advantage to be gained in using QoS to throw away packets, when the packets don't need to be thrown away? > As someone who is looking to deploy VoIP in the near future this is of particular interest. Go ahead and deploy it. It's easy and works well. It certainly doesn't need anything like QoS to make it work. -Bill
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.
participants (3)
-
Bill Woodcock -
Charles Youse -
Valdis.Kletnieks＠vt.edu