[Nice] SIP forking?

mikhail.zabaluev at nokia.com mikhail.zabaluev at nokia.com
Mon Jun 23 05:41:50 PDT 2008


>-----Original Message-----
>From: nice-bounces at lists.freedesktop.org 
>[mailto:nice-bounces at lists.freedesktop.org] On Behalf Of ext 
>Olivier Crête
>Sent: Thursday, June 19, 2008 10:23 PM
>To: nice
>Subject: [Nice] SIP forking?
>I'm in the process of fixing the candidate-setting API in 
>Farsight2. One
>issue where I am not certain how to proceed is SIP forking, since
>libnice doesn't support it yet.
>I guess one would have to set more than one set of remote 
>candidates and
>do connectivity checks with them before selecting the set that will be
>Or would be call set_remote_candidates() with one set of candidates...
>and then if its not the one that's chosen, do a ICE restart and re-set
>the candidates from the chosen partner?

I guess the latter would be much simpler to implement.
However, nice might need to respond to connectivity checks from candidates it doesn't know about yet, and somehow merge the state if these candidates are set at a later time, as the result of a fork resolution.


More information about the Nice mailing list