From: Ales Klok <orrie@seznam.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] voip quality/bandwidth/latency techniques
Date: Fri, 13 Jul 2007 17:09:28 +0000 [thread overview]
Message-ID: <4697B1C8.3010200@seznam.cz> (raw)
In-Reply-To: <46968632.30801@czexan.net>
dale wrote:
> I have voip quality issues I would like to minimize. I have a ~=
> 3M/384k (Comcast) cable modem and a CentOS based Linux router (SME 7,
> 2.6.9 kernel) with 5 NAT'd devices (3 PCs "DHCP", 2 Vonage adapters
> "static 10.10.2.10-11"). The quality problems are audio cutting out
> and popping. I tried the following (see below) based on a Cookbook
> example, but I still have audio popping. I have noticed popping
> corresponding with web browsing, etc. Any suggestions that may
> improve voip quality? Also, are there any network metric
> capture/graphing tools that are helpful to analyze these type of
> issues. I'm thinking of a graph that shows various network metrics.
> I could watch the graph while using the phone and correlate graph
> spikes with audio pops. Thanks in advance for your help.
>
> Dale
Hi Dale, you have to guarantee both delay (latency) and bandwidth for
clean VoIP calls. With HTB you can't do that (although it's still better
than nothing). You should use HFSC scheduler. If you have working HTB
script than changing it to HFSC is quite simple. Good start is here
http://linux-ip.net/articles/hfsc.en/ also there are plenty of exapmles
using HFSC for VoIP on the web. Note that you have to guarantee latency
and bandwidth on both incoming and outgoing direction (i can see only
outgoing in your example). There are other things to tweak such as MTU,
VoIP chunk size and others, but start with HFSC shaping.
/ak
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-07-13 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 19:51 [LARTC] voip quality/bandwidth/latency techniques dale
2007-07-13 17:09 ` Ales Klok [this message]
2007-07-17 1:24 ` Andy Furniss
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=4697B1C8.3010200@seznam.cz \
--to=orrie@seznam.cz \
--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.