Dave Neary wrote:
Adam Gundy wrote:
it looks like there's still no support for STUN with 'other' accounts?
is that planned for 2.2 final?
Why do you say there's no support? Minh, can you comment on the STUN
support in phapi2, please?
I'm absolutely sure phapi/phapi2 support STUN. Openwengo does STUN when
you connect to the wengo servers.
when you ask for an 'other' account however, there is (a) no (easy)
place to specify a STUN server and (b) openwengo doesn't do STUN even if
you poke a STUN server in using the advanced config, or by hand editing
the config files.
last time I looked at the openwengo code (a few weeks ago), there
basically isn't any code to enable STUN in the 'other' class (I forget
what that is now). the 'wengo' variant of that class enables STUN using
some hard coded server on the wengo network...
I assume this is at least partially about making config dialog edits,
and also about not hitting wengo's STUN server for unrelated SIP traffic...
a packet trace of an 'other' login will prove this. openwengo always
announces LAN IP address and port numbers, never public IP/ports.
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
