Bug 22456

Summary:	use fallback conference server during MUC channel creation
Product:	Telepathy	Reporter:	Philippe Normand <phil>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Philippe Normand 2009-06-24 10:02:00 UTC

When requesting a MUC channel with CreateChannel, gabble expects a fully qualified TargetID parameter like foo@conference.server. If the user gives only a muc name without specifying the conference server, gabble should use the fallback server specified in the account

Comment 1 Will Thompson 2010-04-27 03:58:25 UTC

I think Jonny Lamb mostly fixed this a while ago — could you check?

There's an edge case which still won't work: if you request a MUC before Gabble has finished discoing your server to find a conference server, and no fallback is specified, CreateChannel() will fail rather than waiting for the disco to finish.

Comment 2 Will Thompson 2011-01-07 08:25:32 UTC

Yes, Jonny confirms that he fixed this. Here is the implementation:

http://git.collabora.co.uk/?p=telepathy-gabble.git;a=blob;f=src/util.c;h=bfb0443c132c9f2fd6646f2d23e41509c7d3b3f7;hb=HEAD#l441

There is a remaining edge case, bug 25143, but we can mark this bug as fixed in general.

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.