[libnice] STUN request timeouts?

[Olivier Crête]

Hi,

There is a timer inside the STUN code, it is currently hard-coded to
start at 600ms and only re-try 3 times. Our observation was that it
would take too long to timeout when the server didn't exist otherwise.

You can modify it in stun/usages/stuntimer.h by changing
STUN_TIMER_DEFAULT_TIMEOUT and STUN_TIMER_DEFAULT_MAX_RETRANSMISSIONS

Ideally, I guess they should be made runtime configurable as recommended
by RFC 5389 section 7.2.1.

Olivier

On Mon, 2015-03-02 at 16:22 +0100, Miguel París Díaz wrote:
> Hello,
> 
> I am using libnice 0.1.7 into an environment where STUN requests are
> answered in 6 seconds (approximately).
> This cause that "gathering-done" signal is launched before the srflx
> candidates are gathered or if I set "upnp-timeout" property [1] to
> 15000 mseconds the STUN packets are pushed to the user-data callback
> and the candidates are not detected.
> 
> 
> From this observations, are there some hard timeouts into libnice for
> STUN protocol?
> 
> In this case, how can I solve my problem? The timeouts should be
> configurable, or something like that?
> 
> 
> Thanks in advance!!
> 
> 
> [1]
> http://nice.freedesktop.org/libnice/NiceAgent.html#NiceAgent--upnp-timeout
> 
> -- 
> Miguel París Díaz
> ------------------------------------------------------------------------
> Computer/Software engineer.
> Researcher and architect in http://www.kurento.org
> http://twitter.com/mparisdiaz
> ------------------------------------------------------------------------
> 
> _______________________________________________
> nice mailing list
> nice at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nice

-- 
Olivier Crête
olivier.crete at collabora.com