-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 26/01/15 08:51 AM, Dominik George wrote: > Hi, > >> The best first step would probably be to make the TURN relay >> hostname, port, username and password configurable as >> "parameters" in src/protocol.c, the same way the STUN server >> hostname/port and HTTPS proxy hostname/port are currently >> configurable, […] > > I'd even say the existing stun-server parameters could simply be > reused and the UI element be relabled as STUN/TURN-Server. At > least, I cannot see any reason why the STUN server should be > different from the TURN relay, and other clients (including Jitsi) > do that as well. Except that for a TURN server, you need to pass the username and password too. Otherwise it's mostly the same. > Technically, the servers could be split, but as all relevant TURN > server implementations also do STUN and there is no reason to > disable that, I think it is a very safe bet. All TURN servers are also STUN servers, so it's definitely very valid to only supply a TURN server. The annoying part is that you have to pass the TURN server config through telepathy-gabble. TURN servers should really be proposed by the XMPP server, but it seems that no one else than Google went through the effort of designing something that actually works. The Telepathy-Farstream & Farstream part should already support it, so all the work is in Gabble and in Empathy. - -- Olivier Crête [email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEAREIAAYFAlTGbNcACgkQHTiOWk7Zorv1cgCeKBfERBl+3Z0+C5h7x4YFnB+h t9sAnjIdGg4Vgf3O8e8LnLlBHF4G3uoI =ocvb -----END PGP SIGNATURE----- _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
