Re: [rtcweb] Media forking solution for SIP interoperability (without a media gateway)

[Iñaki Baz Castillo <[e-mail]>]

2011/10/31 Christer Holmberg <[e-mail]>:
> I would suggest that, instead of talking about a single PeerConnection, we talk about using the same local IP parameters and candicates for multiple remote endpoints. It could be a single PC, or it could be multiple "cloned" PCs.

Hi Christer, as I replied you in other mail this needs to be clarified:

When are local candidates generated? when creating a new
PeerConnection object? or when creating a new ROAP Offer/Answer
object?

In the first case case you cannot reuse the same local candidates in a
new PeerConnection. In the second case you can do it (if we assume
that first we create a ROAP Offer, it creates local candidates and we
pass the ROAP object to a new PeerConnection) then it would be
possible just if the API allows that.


> Again, let's first decide whether we need it - then we can start thinking of how to get it :)

Assuming the second case above I vote for the API to allow passing an
already used local candidates into a new PeerConnection so we cover
all the media forking cases.



-- 
Iñaki Baz Castillo
<[e-mail]>