All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Info about VoiP Qos
Date: Mon, 24 Jan 2005 22:32:11 +0000	[thread overview]
Message-ID: <41F5776B.3070000@wildgooses.com> (raw)
In-Reply-To: <41F28A25.1030108@e4a.it>


> But i would like to have the possibility to use all the 400Kbps and slow
> down server traffic only when and if needed.
>
> I prioritized VoIP traffic, using the various scripts around, and what i
> get is that, even if voip quality is definitely much much better than
> without shaping, there are is still statics and pops, and some
> interruption of the voice and only if i'm called from POTS
> I do not get this when completely reserving the bandwith or when the
> link is not loaded.


You probably forgot to tweak the HTB code to change the hysterisis value?

This helps a lot with the output stuff.  However, remember that you 
always have to slow down the incoming to a little less than max 
otherwise by the time the stuff is throttled you see some small amount 
of queuing at the remote end.

Also remember that the bandwidth of most adsl links is less than the 
stated bandwidth.  This is because of ATM overheads (which vary 
depending on packet size) and also because the link is contended.

Put this all together and you should be able to get pretty close to 
maximum,. perhaps only reserving a small amount of bandwidth and make 
the rest shareable.

Good luck

Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-01-24 22:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22 17:15 [LARTC] Info about VoiP Qos Riccardo Losselli
2005-01-22 18:11 ` Jason Boxman
2005-01-22 20:03 ` Riccardo Losselli
2005-01-23 20:54 ` Riccardo Losselli
2005-01-24 22:32 ` Ed Wildgoose [this message]
2005-01-25  9:47 ` Riccardo Losselli

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=41F5776B.3070000@wildgooses.com \
    --to=lists@wildgooses.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.