indeed so don't expect a free lunch! also it's particularly bad to assume a behaviour based on a default vendor config. TCP will do the right thing if it's allowed and perhaps that's what Adrian sees (although I expect not all bandwidth is really being consumed or buffering is happening)
I would not always expect that behaviour from UDP especially in large scale high performance environments. (ive seen it not work well). VoIP isn't bandwidth hungry, it's buffering hungry. Sent from my iPad On 7 Jun 2012, at 15:21, "Justin Finkelstein" <[email protected]<mailto:[email protected]>> wrote: Well, yes of course. But not everyone has enough bandwidth.s not On 7 June 2012 15:05, Neil J. McRae <[email protected]<mailto:[email protected]>> wrote: IP networks 101. If you have enough bandwidth everything gets a good deal. Sent from my iPhone On 7 Jun 2012, at 10:42, "Justin Finkelstein" <[email protected]<mailto:[email protected]>> wrote: nteresting; so it sounds, from what you say, that by default VoIP gets a "good deal" isout of the available bandwidth? On 7 June 2012 09:55, Adrian Kennard <[email protected]<mailto:[email protected]>> wrote: On 07/06/12 09:45, Justin Finkelstein wrote: > > This may be the wrong forum for this message, but I was wondering about > how VoIP is handled as part of people's various traffic shaping policies > - i.e. is this something people take account of? Our LNSs know the rate of every line, and shape to match the line rate but with small packets having more priority over large - this works well for VoIP, but also ACK packets, DNS, interactive (key strokes), etc. We find people can fill their line with torrents and still have perfect VoIP calls. > Also: if one of the UK's ISP's decided to implement QoS on their > customer base's users and then prioritise VoIP, what kind of impact > would this have on the upstream network? Upstream is not usually an issue as it is not usually congested!
