Bug 22200

Summary:	Do we really have to send transport-accept immediately for gtalk4?
Product:	Telepathy	Reporter:	Will Thompson <will>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED NOTABUG	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	minor
Priority:	low
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Will Thompson 2009-06-10 03:44:29 UTC

In jingle/incoming-basics.py, I added the following comment:

 # With gtalk4, apparently we have to send transport-accept immediately,
 # not even just before we send our transport-info.
 # FIXME: wjt thinks this is suspicious. It matches the Gabble
 #        implementation, so he moved it here to avoid the test being
 #        racy, but we should do some more interop testing.

It's probably harmless, but I don't know if we actually need it. Maybe we could try removing it and seeing if calling gtalk4 clients still works.

More generally, it'd be good to actually document the quirks of the various Jingle dialects.

Comment 1 Will Thompson 2009-06-23 09:54:21 UTC

I just tested this, and indeed if Gabble doesn't send transport-accept, incoming calls don't work.

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.