From: Leonardo Balliache <leoball@opalsoft.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: LARTC digest, Vol 1 #766 - 9 msgs
Date: Tue, 17 Sep 2002 23:51:20 +0000 [thread overview]
Message-ID: <marc-lartc-103230695410268@msgid-missing> (raw)
Hi,
In a busy network you need to use prio. Check how many channels of voice
you do need and bandwidth required by each channel (16-32 kbits?). Put
voice (udp packets) in the higher priority prio queue and use tbf behind it
to limit traffic via prio to the maximum required for your channels. Or use
htp putting your udp traffic in the higher priority class.
Be careful that higher prio traffic can't be more than 20-30% of the link
capacity to avoid starvation of lower prio traffic.
Don´t expect good quality in a busy network. When congestion appears your
udp packets will be dropped with no mercy (udp is an unresponssive
protocol) hurting quality.
Best regards,
Leonardo Balliache
Ps: Cisco has (check your IOS version) RTP header compression that can help
a lot to lowering bandwidth requirements. You have to enable it at both
sides of the link. Also, why don't try directly with Cisco PQ?
At 06:28 a.m. 17/09/02 +0200, you wrote:
>From: Andreani Luca <landreani@seltatel.it>
>To: "LARTC mailing list (E-mail)" <lartc@mailman.ds9a.nl>
>Date: Mon, 16 Sep 2002 11:49:28 +0200
>Subject: [LARTC] Voip and Qos tests
>
>Hello list,
>
>I'm performing some tests in order to evaluate the possibility to make Voip
>calls on a busy network.
>I use some cisco routers with wfq enabled. I want to introduce some linux
>boxes acting as routers.
>I am especially interested in low-speed (64-128 kbps) links with PPP and
>frame-relay.
>
>Haw you some reference about similar tests?
>
>Whath qdisc (from tc) has best performance in these situations?
>
>Thank's
>
>Luca
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-09-17 23:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-103230695410268@msgid-missing \
--to=leoball@opalsoft.net \
--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.