Bug 93972 - Use custom TURN server
Summary: Use custom TURN server
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-02 20:23 UTC by Fabrice Bellet
Modified: 2016-09-22 01:03 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
util: prefer iceudp transport to google p2p (967 bytes, text/plain)
2016-02-02 20:23 UTC, Fabrice Bellet
Details
call-stream: use relay information from environment variable (1.08 KB, patch)
2016-02-02 20:24 UTC, Fabrice Bellet
Details | Splinter Review
wocky-jingle-info: use relay information from environment variables (3.11 KB, patch)
2016-02-02 20:25 UTC, Fabrice Bellet
Details | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Fabrice Bellet 2016-02-02 20:23:57 UTC
Created attachment 121471 [details]
util: prefer iceudp transport to google p2p

This patch is a workaround to pass relay information (TURN server and credentials) to telepathy-gabble. This patch echoes a discussion that occured on the mailing-list one year ago about the possibility to add a TURN server configuration in empathy:

  http://lists.freedesktop.org/archives/telepathy/2015-January/006649.html

My patch is very simple, as it just reads information from environment variables, the only non-trivial modification is the need to swap the order of the transports in jingle_pick_best_resource(), so ICE UDP is preferred to google p2p.
Comment 1 Fabrice Bellet 2016-02-02 20:24:39 UTC
Created attachment 121472 [details] [review]
call-stream: use relay information from environment variable
Comment 2 Fabrice Bellet 2016-02-02 20:25:20 UTC
Created attachment 121473 [details] [review]
wocky-jingle-info: use relay information from environment  variables


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.