I am trying to configure a small network of ejabberd servers and I am running into problems that the 1st ejabberd server which has a public MUC room returns 503 to stanza addressed to the MUC from a 2nd server. The MUC room and general messaging works for local accounts but not for any non-local accounts.
When I am sending this stanza
<presence to='status@conference.audit.morphbius.com/test@test.morphbius.com/cdn' xmlns='jabber:client'/>
But I am getting back a 503 error.
<presence from='status@conference.audit.morphbius.com/test@test.morphbius.com/cdn' to='test@test.morphbius.com/cdn' type='error' xml:lang='en'><error code='503' type='cancel'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></presence>
The same is happening to <message> stanzas.
I suspect there is a configuration parameter that is incorrect. Would anyone have any suggestions? The ejabberd.cfg file is pretty close to the default. I can provide it if it would be of help.
Regards,
Spencer
Maybe you have this
Maybe you have this FAQ:
http://www.ejabberd.im/subdomains
Domains are fully mapped
All the FQDNs are both DNS mapped (A records) AND defined in /etc/hosts. I also checked the firewalls to make sure it allow port 5269. I have telnet'ed to port 5269 from both direction so the port is open and ejabberd is listening. While I was working on Openfire, I discovered that Openfire configuration requires conference.x.com to be explicitly listed in the whitelist of servers that is allowed to connect or it won't accept
<presence>stanzas.I am currently in the process of rebuilding the virtual machines where ejabberd runs just in case there is something stuck in a cache.
Does ejabberd require SRV records for all domain names?
Is there anything else I should check? Are there any thing in ejabberd.cfg which has to be set/unset?
Should work with default config
Openfire configuration requires conference.x.com to be explicitly listed in the whitelist of servers that is allowed to connect or it won't accept
<presence>stanzas.Are there any thing in ejabberd.cfg which has to be set/unset?
The default ejabberd configuration has mod_muc enabled, working both for local and remote users. From what you say, it should work.