From: "Thomas Switala" <tis@genotribe.com>
To: lartc@vger.kernel.org
Subject: [LARTC] cRTP and RTP or other Header methods of header compression
Date: Wed, 20 Aug 2003 07:02:48 +0000 [thread overview]
Message-ID: <marc-lartc-106136314227258@msgid-missing> (raw)
Hi
I have the following challenges that I need to solve and I did some reading
and I need some input on this as well.
I have a VSAT link at my office and we all know that the more bandwidth we
have the happier we are. I am already
doing some Qos using HTB and IMQ on the link to prioritize specific traffic
and the next challenge I received is
to optimize our Cisco ATA 186 VoIP adaptors. I was looking at doing header
compression between my remote
sites and I was wondering if there is anyone out there that played around
with RTP for Linux and is it possible.
What I typically want to achieve is to have a linux bridged device that
collects the voice packets from the Cisco
and then strips it of all the headers and sends it off to my other office to
another linux bridge and cisco ATA.
Cisco ATA ---- Linux Bridge ---- VSAT --- Internet ----- VSAT -----
Linux Bridge ----- Cisco ATA
I was also thinking about doing PPPoE between the two Linux Bridges and from
what I have read they tell me
that I will only get 5 -10 % bandwidth saving. Is there any other method
that you guys recommend that I have
a look at.
Hope to hear from you soon
Thomas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-08-20 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 7:02 Thomas Switala [this message]
2003-08-20 7:43 ` [LARTC] cRTP and RTP or other Header methods of header Eric Leblond
2003-08-25 7:51 ` [LARTC] cRTP and RTP or other Header methods of headercompression Thomas Switala
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-106136314227258@msgid-missing \
--to=tis@genotribe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox