Re: Contributing sources

I was pretty much relying on this functionality and I did not realize it 
had not been implemented 8-).  I would be happy to help contribute.  
addContributor and removeContributor would work quite nicely.  On the 
receiving side, it would be nice to have some sort of notification for 
when a new CSRC is seen and when one leaves. 

Also, is there any way to get an IP address, given a CSRC?  (on the 
recieving side, that is). 

Let my know what you had in mind, and your general strategy, etc.

Federico Montesino Pouzols wrote:
> Yes, the  API for handling CSRC values in outgoing packets is half missing
> (some methods as the one you mention are declared but not implemented).
> Most of the low level functionality for handling contributors is however
> implemented, so it's a matter of coming up with a good API to set CSRCs
> for the outgoing queue and implement it. This item has been for a long
> time in
> the TODO list but since it hasn't been requested so far, it has been sort of
> forgot.
>
> Would the currently declared methods (addContributor and removeContributor)
> work for you? I'll probably look into this issue within a few days, so any
> suggestion or contribution would be very welcomed.
>
>
>
>
>