On 04/06/16 20:21, Diane Trout wrote: > On Tue, 2016-04-26 at 17:52 +0200, Daniel Pocock wrote: >> Finally, for media streaming, it would be good to come up with a >> common >> solution for both telepathy-resiprocate and telepathy-gabble (or a >> TelepathyQt-based successor to it). This would potentially mean >> using >> the same TURN server parameters for either protocol. Maybe Farstream >> is >> relevant to this, but I haven't looked at that closely enough yet. >> Whatever approach we use for media streaming, we should aim to >> eventually have full WebRTC interoperability, one way to get that is >> to >> use the media stack from Chromium. > > Farstream is a set of gstreamer plugins that handles all the RTC. > > As far as I can tell farstream only uses stun_usage_bind_create from > libnice, I didn't see anything about TURN. > > Though it does look like libnice has TURN support. > > What TURN settings should telepathy be trying to use?
TURN URI (comprising hostname, protocol and port) Username Password Client certificate (for TLS) HTTP proxy settings from the system-wide environment could also be used to access TURN using the HTTP CONNECT method. The credentials (Username, Password, Client certificate) could be the same as those used by the signaling protocol (SIP or XMPP) TURN URIs are described here: https://tools.ietf.org/html/rfc7065 These are also worth looking at: https://bugs.chromium.org/p/chromium/issues/detail?id=559115 https://bugzilla.mozilla.org/show_bug.cgi?id=1226550 _______________________________________________ telepathy mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/telepathy
