Bug 25961 - Discover STUN servers via DNS SRV
Summary: Discover STUN servers via DNS SRV
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks: 25385 57546
  Show dependency treegraph
 
Reported: 2010-01-09 04:13 UTC by Dennis Schridde
Modified: 2012-12-06 12:29 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Dennis Schridde 2010-01-09 04:13:01 UTC
Telepathy/Gabble should use DNS SRV requests to discover STUN servers for the domain it connects to. (I.e. _stun._udp.domain.tld if the JID is user@domain.tld)
Comment 1 Mike Ruprecht 2010-02-09 21:46:57 UTC
Here's my patch for this bug:
http://git.collabora.co.uk/?p=user/maiku/telepathy-gabble.git;a=shortlog;h=refs/heads/bug-25961
Comment 2 Mike Ruprecht 2010-02-22 18:27:10 UTC
Updated the branch per our discussion. http://git.collabora.co.uk/?p=user/maiku/telepathy-gabble.git;a=shortlog;h=refs/heads/bug-25961
Comment 3 Will Thompson 2012-11-23 17:37:48 UTC
I started reviving this branch, but because of some pretty major changes to Gabble (Call moved to tp-glib, and I split the Jingle code in half with a view to it landing in Wocky) I have basically ended up redoing the branch: rebasing/merging was more work (I did try to do them first).

Still a work in progress: http://cgit.collabora.com/git/user/wjt/telepathy-gabble/log/?h=25961-stun-srv

I took the approach of integrating the SRV lookups with the existing code in a similar way to the initial google:jingleinfo lookup, which does have the downside of only making a single lookup at connection time (so the results could get stale) but avoids having two very similar paths and duplicated code.
Comment 4 Will Thompson 2012-12-06 12:29:20 UTC
I merged this to master for 0.17.2.


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.