Thanks for the info. Is Trickle being worked on right now, or would it be possible to fund an eventual Trickle implementation? Also with vanilla ICE the next candidate would have to be tried at some point, but that doesn't seem to happen. Is there a configurable candidate timeout property for this? Thanks a lot Von: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> Im Auftrag von krice@freeswitch.org Gesendet: Donnerstag, 19. August 2021 18:32 An: 'FreeSWITCH Users Help' <freeswitch-users@lists.freeswitch.org> Betreff: Re: [Freeswitch-users] ICE -> FreeSWITCH tries exclusively the first candidate Freeswitch at this time does not support trickle ice From: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org<mailto:freeswitch-users-bounces@lists.freeswitch.org>> On Behalf Of Alexander Haugg Sent: Tuesday, August 10, 2021 12:53 AM To: freeswitch-users@lists.freeswitch.org<mailto:freeswitch-users@lists.freeswitch.org> Subject: [Freeswitch-users] ICE -> FreeSWITCH tries exclusively the first candidate Hi, currently I have the problem that the FreeSWITCH only serves the first candidate from the candidate list via STUN request. I expected it to try to reach all candidates relatively soon (trickle). In the source code I saw that there are four ICE types: ICE_GOOGLE_JINGLE ICE_VANILLA ICE_CONTROLLED ICE_LITE What is behind them, and how can I select them from the "outside"? Or am I on the wrong track? What to do, that the FreeSwitch serves the candidates according to Trickle? I have the same result for mod_sofia and mod_verto (is clear, they use the same media stack). Thanks and greetings Alex