STUN RFC3489 vs 5389

[Diane Trout]

Actually that patch appears to have not have worked. Though I'm not sure if 
its because I didn't know how to proprely get the new farstream library loaded 
or if the ktp-call-ui/TelepathyQt stack was initializing a different 
transmitter.




On Sunday, May 19, 2013 22:04:15 Diane Trout wrote:
> Hello,
> 
> I was having trouble using kde-telepathy call-ui (using farstream 0.1) to
> call jitsi over xmpp on a NATted network. I was able to have jitsi call
> itself, and a nokia N9.
> 
> I packet sniffed and discovered that jitsi was using the RFC5389 version of
> STUN, while ktp-call-ui + farstream was using the RFC3489 version.
> 
> Most of the documentation about STUN say the older version doesn't work very
> well. It looks like libnice supports both versions,
> 
> Has anyone considered doing something like this? (No idea if the AGENT_USAGE
> flags are a good idea or not).
> 
> Diane
> 
> diff --git a/transmitters/rawudp/fs-rawudp-component.c
> b/transmitters/rawudp/fs-rawudp-component.c
> index 156450c..25fa8ca 100644
> --- a/transmitters/rawudp/fs-rawudp-component.c
> +++ b/transmitters/rawudp/fs-rawudp-component.c
> @@ -509,7 +509,9 @@ fs_rawudp_component_init (FsRawUdpComponent *self)
>    self->priv->associate_on_source = TRUE;
> 
>    stun_agent_init (&self->priv->stun_agent,
> -      STUN_ALL_KNOWN_ATTRIBUTES, STUN_COMPATIBILITY_RFC3489, 0);
> +      STUN_ALL_KNOWN_ATTRIBUTES,
> +      STUN_COMPATIBILITY_RFC5389,
> +      STUN_AGENT_USAGE_ADD_SOFTWARE | STUN_AGENT_USAGE_USE_FINGERPRINT);
> 
>  #ifdef HAVE_GUPNP
>    self->priv->upnp_mapping = TRUE;
> 
> _______________________________________________
> Farstream-devel mailing list
> Farstream-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/farstream-devel