Hi Olivier, Thanks for the super-fast answer! And sorry for the dumb question, I didn't know this had already been tested with compliant Jingle implementations. I'll give it a try in Janus as well and let you know if I encounter any issue with it. Thanks! Lorenzo <div class="gmail_quote">Il 22/apr/2014 18:07 "Olivier Crête" <<a href="mailto:olivier.crete@collabora.com">olivier.crete@collabora.com</a>> ha scritto: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi On Tue, 2014-04-22 at 17:43 +0200, Lorenzo Miniero wrote: > Do you have any suggestion on how this could be achieved? Are there > plans to include support for actual Trickle in the library in the > future, by the way? Trickle is already supported as it has been how XMPP Jingle has been using ICE since the beginning. The secret recipe is to ignore state changes to the "FAILED" state and just keep on adding remote candidates. Adding candidates to a "FAILED" component will just make the ICE processing continue with these new candidates. Once you know for sure that the candidates have all been received, then FAILED is final. Also, in the upcoming 0.1.6 release, I've added the ability to add TURN servers after the initial gathering phase to be able to support the Google-like system where they only connect to the TURN servers have a little delay to reduce load on the TURN servers if a direct connection can quickly be established. -- Olivier Crête <a href="mailto:olivier.crete@collabora.com">olivier.crete@collabora.com</a> </blockquote></div>