[Jingle] WebRTC + Jingle - Incomplete SDP

Peter Thatcher pthatcher at google.com
Tue Jun 25 18:21:51 UTC 2013

FYI, It's also possible to have multiple streams within a <content> and
then demux by ssrc, which gives multiple audio or video streams over a
single transport without using BUNDLE.  You can see an implementation of
such here in libjingle:


It's never been standardized, but we've found it to work well in practice,
and it looks kind of like this:

      <!-- ... codecs and stuff -->
        <stream name="stream1">
        <stream name="stream2">

PS: This is like the RTCWEB "Plan A vs Plan B" all over again :).

On Tue, Jun 25, 2013 at 4:40 AM, Philipp Hancke
<fippo at goodadvice.pages.de>wrote:

>  By the way, I have a short question about the Jingle <description />
>> element. In case I have 2 media streams, both audio and video, that are
>> synchronous (a webcam stream for example):
>> 1. Should I create 2 <content /> elements as I can see on
>> http://xmpp.org/extensions/**xep-0293.html#sdp-mapping<http://xmpp.org/extensions/xep-0293.html#sdp-mapping>
>>  ?
>> 2. Or create one single <content /> element, name it something like
>> 'conference', and append 1 single <transport /> element with 2 <description
>> /> elements, one media="audio" and another media="video"?
>> ATM I implemented the 2. way, but I'm not sure it's the correct one since
>> it is not explicitly explained in XEP-0166. But after Philipp sent me a
>> list of useful Jingle XEPs for my implementation, and I found out the XML
>> scheme from the link in 1., I have doubts.
> use two <content/>s, they basically map to an sdp mline. The
> synchronization is implicit by having them in the same session.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jingle/attachments/20130625/00c4cc74/attachment.html>

More information about the Jingle mailing list