[ejabberd] iChat and mod_muc / s2s

Konstantin Khomoutov flatworm at users.sourceforge.net
Fri May 28 16:36:14 MSD 2010

On Fri, 28 May 2010 23:28:13 +1200
David Young <davidy at funkypenguin.co.nz> wrote:

> We've been playing with iChat.app on OSX Snow Leopard, and it works
> well (as expected) with our ejabberd server.
> I'm interested in the feature which lets you invite multiple users to
> chat.. to me, this looks like dynamic creation of a MUC, which would
> be really handy for our mostly-Mac team.
> However, when I I try to invite a (internal) contact to a chat, I get
> a message like this:
> --------
> =INFO REPORT==== 2010-05-28 23:20:41 ===
> I(<0.1388.0>:ejabberd_s2s:368) : New s2s connection started <0.1389.0>
> =INFO REPORT==== 2010-05-28 23:20:41 ===
> I(<0.1389.0>:ejabberd_s2s_out:1148) : Trying to open s2s connection:
> jabber.mydomain.com -> chat315042937127785653
> =INFO REPORT==== 2010-05-28 23:20:42 ===
> I(<0.1389.0>:ejabberd_s2s_out:227) : s2s connection:
> jabber.mydomain.com -> chat315042937127785653 (remote server not
> found)
> ---------
> On each attempt, the numbers after "chat" differ, which is why I
> assume it's a randomly created MUC room.
> It doesn't look as if iChat is adding my FQDN after the chat name, or
> in fact, as if it's a MUC at all (s2s connection is mentioned).
> Has anybody had success getting iChat.app to interoperate with
> ejabberd?

Does "usual" process of joining a MUC room work for you?
That is, can you navigate to your MUC service node and join a room

>From the ejabberd log it appears that you either have MUC service not
configured or some sort of DNS problem so that your jabber.mydomain.com
does not resolve to the IP of the machine serving MUC.

More information about the ejabberd mailing list