Rtp Header Extension
GoogleCodeExporter opened this issue · 4 comments
GoogleCodeExporter commented
Gtalk plugin uses an extra header in the Rtp Header, called Rtp Header
Extension. Does anyone know the purpose of this header and if is possible to
tell to gtalk plugin (during the XMPP negotiation) to not use this header? The
MediaChannel class defines RtpHeaderExtension struct and these functions (that
you must to override):
virtual bool SetRecvRtpHeaderExtensions(
const std::vector<RtpHeaderExtension>& extensions) = 0;
virtual bool SetSendRtpHeaderExtensions(
const std::vector<RtpHeaderExtension>& extensions) = 0;
What's the difference between SetRecv and SetSend? Is it possible to use these
functions to disable the use of this header? Also, it seems that linphone
cannot handle Rtp header extensions. Does anyone know anything about this?
Thanks in advance.
Original issue reported on code.google.com by diego.cd...@gmail.com
on 31 Aug 2011 at 2:52
GoogleCodeExporter commented
Hi, currently I just simply ignore the extension, maybe it's used for quality
control?
Regards
Original comment by interfac...@gmail.com
on 1 Sep 2011 at 10:00
GoogleCodeExporter commented
Hi, I'm also ignoring the header. But I would like to know if there is a way to
tell to Gmail plugin to not use it. Thanks.
Original comment by diego.cd...@gmail.com
on 1 Sep 2011 at 1:40
GoogleCodeExporter commented
There is an experimental XMPP extension
(http://xmpp.org/extensions/xep-0294.html) to negotiate the use or not of the
RTP Header Extension along with the codecs on session-initiate. Is there,
currently, something like this at Google's side? A way to tell that I don't
want to receive it.
Original comment by diego.cd...@gmail.com
on 6 Oct 2011 at 11:58
GoogleCodeExporter commented
Removing all bugs regarding the Google Talk/Hangouts plugin.
Original comment by juberti@google.com
on 31 May 2013 at 3:51
- Changed state: WontFix