From: sam@ravnborg.org
To: Matevz Langus <matevy@arhitektova-delavnica.com>
Cc: linuxppc-dev@lists.linuxppc.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Efficient handling of RTP frames?
Date: Tue, 11 May 2004 23:42:43 +0200 (CEST) [thread overview]
Message-ID: <20040511214243.A2ED715C57@post1.dk> (raw)
Tir, 11 May 2004 10:28:02 +0200 skrev Matevz Langus <matevy@arhitektova-delavnica.com> :
>Hi,
>
>I did the following in advance to all others said before:
>left UDP CRC field empty, so you don't need to calculated CRC. VoIP
>systems do not complain about that.
Thanks for this tip, unfortunately we already use this 'feature'.
We are operating with 5 ms samples so we need to be very careful about any overhead (present implementation is running in a VxWorks environment).
Sam
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-05-11 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 21:42 sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 20:58 Efficient handling of RTP frames? Sam Ravnborg
2004-05-10 21:16 ` Dan Malek
2004-05-10 21:33 ` Sam Ravnborg
2004-05-11 1:55 ` Dan Malek
2004-05-10 22:22 ` Eugene Surovegin
2004-05-11 8:28 ` Matevz Langus
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=20040511214243.A2ED715C57@post1.dk \
--to=sam@ravnborg.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=matevy@arhitektova-delavnica.com \
/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;
as well as URLs for NNTP newsgroup(s).