From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Voip QOS
Date: Mon, 10 Jun 2002 20:25:48 +0000 [thread overview]
Message-ID: <marc-lartc-102374079609354@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102373851006562@msgid-missing>
On Monday 10 June 2002 21:50, Muhammed Soyer wrote:
> Hi,
> I have an 128K wan connection to one of my offices. We are using VOIP
> on this connection ..We also carry our data traffic on this line ..Some
> time , when the data traffic is high , the voice quality drops drastically
> .. I have tried prio queues ..I let the voice traffic use the first band
> ..And the other data tarffic third band .. This makes things a little
> better ..But not quite well ..
> An other problem is ..I both want to priotize and shape my traffic ..
> For example ..I want to limit the mail traffic to some kbits ..While I am
> letting the voice traffic the best priority .. I try to use HTB with PRIO
> qdisc ..But couldnt be succesfull ..
>
> What do you suggest me to make the voice quality good enough ..and shape
> the data traffic related to some criteria ?
What are the requirements for a good VOIP link? Steady bandwidth, low
latency, low jitter, ...
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-06-10 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 19:50 [LARTC] Voip QOS Muhammed Soyer
2002-06-10 20:17 ` King Yung Tong
2002-06-10 20:25 ` Stef Coene [this message]
2002-06-10 20:34 ` Michael T. Babcock
2002-06-14 7:27 ` Muhammed Soyer
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=marc-lartc-102374079609354@msgid-missing \
--to=stef.coene@docum.org \
--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.