There are two aspects to QoS that you have direct control over: 1) traffic leaving your network (easy to QoS since you (most of the time) have access to the egress equipment) and 2) traffic arriving on your end-point which is harder to do, but more and more service providers are assisting with QoS on that final ingress link to your network to ensure timely delivery of voice vs your regular traffic. Ray Burkholder

-----Original Message----- From: Bill Woodcock [mailto:woody@pch.net] Sent: February 10, 2003 13:58 To: Stephen J. Wilcox Cc: nanog@nanog.org Subject: Re: VoIP QOS best practices

> However, its important that the backbone is operating "properly" ie not > saturated which I think should be the case for all network operators, theres a > requirement tho if the customer has a relatively low bandwidth tail to the > network which is shared for different applications, its probably a good idea to > make sure the voip packets have higher priority than non-realtime data... (this > last comment is a suggestion, I've not actually tested this in a real > environment, low b/w lab tests tend to exclude other traffic flows)

We've got plenty of the INOC-DBA phones on the ends of congested satellite tail-circuits, and don't really have significant trouble. As has been pointed out, the VoIP traffic may be stomping all over TCP traffic on the same links, but it _sounds_ good. :-)

-Bill