From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: lartc@vger.kernel.org
Subject: [LARTC] QoS for VoIP
Date: Thu, 27 Sep 2007 02:31:08 +0000 [thread overview]
Message-ID: <00c701c800ae$762e8990$0100a8c0@MingChing> (raw)
In-Reply-To: <marc-lartc-107000832316611@msgid-missing>
As you are probably aware, this is a ever green topic.
I have personally tried doing it, testing it and verifying it
and I am myself finding this problem challenging and frustrating.
Most of the scripts will recommend some form of rate limiting
( or policing ) on the download. But the challenge is how to
determine the correct value for the policing ?
Lot of the recommendation says use x % over the sales package
figure. Is this the correct way to do it ? Should it be a more
engineering way to empirically determine it ?
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.
Any views or comments ?
--------------------------------------------
Important Warning!
***************************
This electronic communication (including any attached files) may contain confidential and/or legally privileged information and is only intended for the use of the person to whom it is addressed. If you are not the intended recipient, you do not have permission to read, use, disseminate, distribute, copy or retain any part of this communication or its attachments in any form. If this e-mail was sent to you by mistake, please take the time to notify the sender so that they can identify the problem and avoid any more mistakes in sending e-mail to you. The unauthorised use of information contained in this communication or its attachments may result in legal action against any person who uses it.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-27 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 8:12 [LARTC] QoS for VoIP Craig Main
2003-11-28 18:05 ` Kilian Krause
2007-09-27 2:31 ` Ming-Ching Tiew [this message]
2007-09-27 16:05 ` Santiago
2007-09-28 1:09 ` Ming-Ching Tiew
2007-09-28 2:45 ` Santiago
2007-09-28 14:07 ` Santiago
2007-10-01 1:00 ` Ming-Ching Tiew
-- strict thread matches above, loose matches on Subject: below --
2004-07-16 15:19 [LARTC] QoS for Voip Alessandro Ren
2004-07-16 15:53 ` Andreas Klauer
2004-07-16 16:54 ` Jason Boxman
2004-07-16 17:51 ` ibro tj
2004-07-16 18:38 ` Andreas Klauer
2004-07-19 12:45 ` Alessandro Ren
2004-07-19 13:19 ` Andreas Klauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00c701c800ae$762e8990$0100a8c0@MingChing' \
--to=mingching.tiew@redtone.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.