[libnice] Regarding libnice signals: component-state-changed and new-selected-pair

[Anand Sivaram]

Thanks for the reply Olivier.  Let me collect the log and I will file a bug.

Anand

On 20 October 2016 at 19:42, Olivier Crête <olivier.crete at collabora.com>
wrote:

> Hello,
>
> That definitely looks like you're hitting some kind of bug. Can you please
> file it at https://phabricator.freedesktop.org/maniphest/
> task/edit/form/1/?tag=libnice and attach a log that you can create with
> G_MESSAGES_DEBUG=all
>
> Olivier
>
> On Thu, 2016-10-20 at 19:13 +0530, Anand Sivaram wrote:
>
> Dear All,
>
> I find the following problem happening *occasionally* with libnice latest
> code.
>
> The stream/component is getting "component-state-changed" signal
> to state "READY" but the signals "new-selected-pair" or
> "new-selected-pair-full" are not getting called.
>
> This happens even when both peers are on the same local LAN where in normal
> working case they select the host candidates.
>
> In my application code, I assume both READY state and
> "new-selected-pair" should have occurred before declaring the component
> to be usable.  Due to this, my application is not getting connected.
>
> Q1. If I depend only on READY state, is it well enough?
>
> Q2. I was wondering why "new-selected-pair" signal is missing even though
> the state is getting changed to READY.  Is it normal to be like that?
>
> Thanks and Regards
>
> Anand
>
>
>
> _______________________________________________
> nice mailing listnice at lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/nice
>
> --
>
> Olivier Crête olivier.crete at collabora.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/nice/attachments/20161023/70f1dc86/attachment.html>