Always use Google jingle when the other end supports, will have to do this cpw.malu.xmpp.google_relay

Mon, 21 Sep 2009 20:58:03 +0000

author
Marcus Lundblad <malu@pidgin.im>
date
Mon, 21 Sep 2009 20:58:03 +0000
branch
cpw.malu.xmpp.google_relay
changeset 28446
b81b650a5dc7
parent 28445
c3dbe0b64f44
child 28564
284bd8fdc5fa

Always use Google jingle when the other end supports, will have to do this
to take advantage of the relays (since it needs Google compat. ICE params).
The relay address fetching is still unfinished, so calling with this code is
currently broken...

libpurple/protocols/jabber/jabber.c file | annotate | diff | comparison | revisions
--- a/libpurple/protocols/jabber/jabber.c	Mon Aug 31 20:23:51 2009 +0000
+++ b/libpurple/protocols/jabber/jabber.c	Mon Sep 21 20:58:03 2009 +0000
@@ -3033,12 +3033,9 @@
 		jbr = jabber_buddy_find_resource(jb, resource);
 		g_free(resource);
 
-		/*
-		return jabber_google_session_initiate(js, who, type);
-		*/
+		/* if we are on a Google Talk connection and the remote supports
+		 Google Jingle, we will go with that */
 		if (type & PURPLE_MEDIA_AUDIO &&
-				!jabber_resource_has_capability(jbr,
-				JINGLE_APP_RTP_SUPPORT_AUDIO) &&
 				jabber_resource_has_capability(jbr,
 				GOOGLE_VOICE_CAP))
 			return jabber_google_session_initiate(js, who, type);

mercurial