[libnice] Regarding libnice signals: component-state-changed and new-selected-pair
aspnair at gmail.com
Thu Oct 27 05:34:04 UTC 2016
It took some time to get the log. Sorry for the delay. I filed a new
Thanks and Regards
On 23 October 2016 at 09:28, Anand Sivaram <aspnair at gmail.com> wrote:
> Thanks for the reply Olivier. Let me collect the log and I will file a
> On 20 October 2016 at 19:42, Olivier Crête <olivier.crete at collabora.com>
>> That definitely looks like you're hitting some kind of bug. Can you
>> please file it at https://phabricator.freedes
>> ktop.org/maniphest/task/edit/form/1/?tag=libnice and attach a log that
>> you can create with G_MESSAGES_DEBUG=all
>> On Thu, 2016-10-20 at 19:13 +0530, Anand Sivaram wrote:
>> Dear All,
>> I find the following problem happening *occasionally* with libnice latest
>> 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
>> 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
>> 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...
More information about the nice