From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Voip QOS
Date: Mon, 10 Jun 2002 20:34:39 +0000 [thread overview]
Message-ID: <marc-lartc-102374133309828@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102373851006562@msgid-missing>
Stef Coene wrote:
>What are the requirements for a good VOIP link? Steady bandwidth, low
>latency, low jitter, ...
>
>
All of the above, in my experience. Depending on the protocol, good
bandwidth (as opposed to perfect) and very low latency are required.
Bandwidth equal to the target bandwidth with very low latency and no
fragmentation is perfect. Part of the problem is not knowing your
maximum number of VOIP links.
In a perfect world, one would use PRIO and mark the VOIP packets as "go
now ... do not pass go, do not collect $200".
--
Michael T. Babcock
_______________________________________________
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:34 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
2002-06-10 20:34 ` Michael T. Babcock [this message]
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-102374133309828@msgid-missing \
--to=mbabcock@fibrespeed.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.