[Jingle] Identifying the source of media

[Peter Saint-Andre]

Olivier Crête wrote:
> On Mon, 2009-02-16 at 12:15 -0700, Peter Saint-Andre wrote:
>> <snip/>
>>
>>>         > Indicating what SSRC the sender should send won't work with older
>>>         > clients who don't expect the SSRC attribute (and therefore
>>>         will pick a
>>>         > random SSRC).
>>>
>>>         I agree that telling someone else what SSRC they should be
>>>         sending is
>>>         problematic (and very hard to do in the server-less case..)
>>>
>>>
>>>     I still think it's useful in the server-based case to avoid
>>>     collisions. But we can continue to discuss that separately...
>>>
>>>
>>> I also think the ability to identify the streams using SSRC in case of a
>>> pure jingle call (no Mingle) is still useful, if the receiving client
>>> decides to have all the RTP media streams multiplexed over the same UDP
>>> port.
>> So, do we need a way to include the SSRC? If so, where in the signalling
>> does it belong?
> 
> I'd suggest either an optional attribute in <description> or an optional
> child to <description>.

I prefer an attribute:

<description
    xmlns='urn:xmpp:jingle:apps:rtp:1'
    media='audio'
    ssrc='0x8b3baa9f'>
...
</description>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/jingle/attachments/20090216/3fb95e5e/attachment.bin