[55757] in North American Network Operators' Group
Re: VoIP QOS best practices
daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Feb 10 14:41:50 2003
Date: Mon, 10 Feb 2003 13:52:03 -0500
Cc: Jared Mauch <jared@puck.nether.net>,
Charles Youse <cyouse@register.com>, nanog@nanog.org
To: Bill Woodcock <woody@pch.net>
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <Pine.GSO.4.44.0302101018450.13545-100000@paixhost.pch.net>
Errors-To: owner-nanog-outgoing@merit.edu
You're specifically talking about the g728a codec?
I typically have been using g711ulaw which is a 64k vs the g728a codec
that is 8k.
Aside from that, Bill is quite correct here. There's little need for
QoS other than at the edge of ones network to insure that your circuit
is not full of other streaming media applications that put your tcp
performance in the toilet.
- jared
On Monday, February 10, 2003, at 01:19 PM, Bill Woodcock wrote:
>
>> My main concern is that some of the sites that will be tied with
>> VoIP have only T-1 data connectivity, and I don't want a surge in
>> traffic to degrade the voice quality, or cause disconnections or
>> what-have-you. People are more accustomed to data networks going
>> down; voice networks going down will make people shout.
>
> It works fine on 64k connections, okay on many 9600bps connections.
> T1 is
> way more than is necessary.
>
> -Bill
>
