[libnice] Dropping old remote candidates without stream/agent restart

Olivier Crête olivier.crete at collabora.com
Sat May 2 19:16:26 PDT 2015


This is exactly what ICE restart is for, if the remote candidates 
change, you also want to change the ufrag/pwd. Changing the ufrag/pwd 
is normally how you instruct the other side to do a restart.

The restart does NOT reset the local candidates, they will be exactly 
the same.

Ref: http://tools.ietf.org/html/rfc5245#section-


On Sun, 2015-05-03 at 03:34 +0200, Ilya Konstantinov wrote:
> Hi,
> Is it possible to reset the remote candidates only? In my scenario, 
> I'm suspecting the remote offer might've changed, e.g.:
> - remote host roamed to a different network
> - remote app restarted (auth and ports changed)
> In such case, let’s assume my app can refresh the remote 
> candidates by querying the signalling server for them.
> How can I make libnice consider re-negotiation? Naïvely using 
> nice_agent_set_remote_candidates just appends them, and if the 
> previous ones are deemed good enough, the new ones won't be 
> considered. Ideally I'd like to drop the old remote candidates 
> entirely (unless they repeat in the new set of remote candidates).
> There’s nice_agent_restart and nice_agent_stream_restart, but both 
> of them also reset the local candidates and auth, which isn’t my 
> goal at all.
> Thanks
> _______________________________________________
> nice mailing list
> nice at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nice
Olivier Crête
olivier.crete at collabora.com

More information about the nice mailing list