From: "Santiago" Date: Fri, 28 Sep 2007 14:07:10 +0000 Subject: Re: [LARTC] QoS for VoIP Message-Id: <20070928140350.M405@elportal.net.ec> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org If you have for example 1024 Kbps, you have to create a class (maybe htb)=20 about 920Kpbs to create the queue. Then you have to attach the prio qdisc t= o=20 this class, mark the voip packets and send to class :1 in the prio qdisc. Santiago Ecuador On Thu, 27 Sep 2007 12:05:16 -0400, Santiago wrote > The prio qdisc is the solution. Try this. >=20 > On Thu, 27 Sep 2007 10:31:08 +0800, Ming-Ching Tiew wrote > > As you are probably aware, this is a ever green topic. > >=20 > > I have personally tried doing it, testing it and verifying it > > and I am myself finding this problem challenging and frustrating. > >=20 > > Most of the scripts will recommend some form of rate limiting > > ( or policing ) on the download. But the challenge is how to=20 > > determine the correct value for the policing ? > >=20 > > Lot of the recommendation says use x % over the sales package=20 > > figure. Is this the correct way to do it ? Should it be a more > > engineering way to empirically determine it ? > >=20 > > What I noticed is that if I over-specify the x %, then I > > will greatly limit the utilizable bandwidth. The LAN users will > > noticed significant difference in download speed compared > > to when QoS is not running. But if I under specify the > > x %, then the entire VoIP QoS has no significance, and > > the VoIP quality will be bad. > >=20 > > Any views or comments ? > >=20 > > -------------------------------------------- > > Important Warning! > >=20 > > *************************** > >=20 > > This electronic communication (including any attached files) may=20 > > contain confidential and/or legally privileged information and is=20 > > only intended for the use of the person to whom it is addressed. If=20 > > you are not the intended recipient, you do not have permission to=20 > > read, use, disseminate, distribute, copy or retain any part of this=20 > > communication or its attachments in any form. If this e-mail was=20 > > sent to you by mistake, please take the time to notify the sender so=20 > > that they can identify the problem and avoid any more mistakes in=20 > > sending e-mail to you. The unauthorised use of information contained=20 > > in this communication or its attachments may result in legal action=20 > > against any person who uses it. > >=20 > > _______________________________________________ > > LARTC mailing list > > LARTC@mailman.ds9a.nl > > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc > >=20 > > --=20 > > Este mensaje ha sido analizado por MailScanner > > en busca de virus y otros contenidos peligrosos, > > y se considera que est=E1 limpio. > > MailScanner agradece a transtec Computers por su apoyo. >=20 > -- > Open WebMail Project (http://openwebmail.org) >=20 > --=20 > Este mensaje ha sido analizado por MailScanner > en busca de virus y otros contenidos peligrosos, > y se considera que est=E1 limpio. > MailScanner agradece a transtec Computers por su apoyo. >=20 > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc -- Open WebMail Project (http://openwebmail.org) --=20 Este mensaje ha sido analizado por MailScanner en busca de virus y otros contenidos peligrosos, y se considera que est=E1 limpio. MailScanner agradece a transtec Computers por su apoyo. _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc