setLocalDescription starts candidate gathering?

[Tobias Guennewig]

Hello,

is it correct behaviour, that onicecandidate gets only called after i
called setLocalDescription?
I always have to call createOffer and call setLocalDescription with
the SessionDescription created by createOffer. Unfotunately the
created offer does not include any candidates, so that i call
createOffer and setLocalDescription again, after icecandidate was
called with a null candidate. Am i doing something wrong?

Thanks in advance

[Vikas]

I think that is right, candidate allocation will only be initiated
when SetLocalDescription is called.

/Vikas

On Nov 18, 11:28 am, Tobias Guennewig

[Tobias Guennewig]

Thanks for your reply. I dont like the behaviour though :)

[Harald Alvestrand]

On Wed, Nov 21, 2012 at 3:57 PM, Tobias Guennewig <tobias.g...@googlemail.com> wrote:

Thanks for your reply. I dont like the behaviour though :)

The problem is that until setLocalDescription() is done, we have no idea how many candidates we will need, because that depends on the number of m= lines and the bundle option.

We had discussions in Lyon last month about providing "preallocated" candidates, with some controls to control how many candidates to gather and when, but this is likely to be an "advanced feature" - too many things can go wrong.

 

--

[hoangtuansu]

@Vikas

About this behaviour, when working with apprtc, I saw that the offerer also sends some "a=candidate..." messages to server after sending the offer message. Upon receiving the offer, it immediately creates an answer with several "a=candidate" messages and send them to server. After that the "a=candidate" messages from the offerer are processed.