On Fri, 2008-12-19 at 13:19 -0500, Youness Alaoui wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Olivier Crête wrote:
> > On Tue, 2008-12-16 at 20:19 -0500, Youness Alaoui wrote:
> >> Olivier Crête wrote:
> >>> Also, also add a way to add/remove/list the ssrcs that can be
> >>> remov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olivier Crête wrote:
> On Tue, 2008-12-16 at 20:19 -0500, Youness Alaoui wrote:
>> Olivier Crête wrote:
>>> Also, also add a way to add/remove/list the ssrcs that can be
>>> removed by a stream.
>>
>> humm.. this I don't really understand, if you co
On Tue, 2008-12-16 at 20:19 -0500, Youness Alaoui wrote:
> Olivier Crête wrote:
> > Also, also add a way to add/remove/list the ssrcs that can be
> > removed by a stream.
>
> humm.. this I don't really understand, if you could elaborate on that,
> it would be nice.
Some protocols (SIP with RF
Olivier Crête wrote:
> Hello,
>
> I've been wondering about this for a while. Having the cname in the base
> API in fs_conference_new_participant() was probably not a great idea. It
> seems that the various SSRCs can be associated with a stream using
> various techniques.
>
indeed not a great id
Hello,
I've been wondering about this for a while. Having the cname in the base
API in fs_conference_new_participant() was probably not a great idea. It
seems that the various SSRCs can be associated with a stream using
various techniques.
So I'd like to propose the following API change (since we
