[jadmin] Unable to create/join conference room when logged in on another s erver

Peter Saint-Andre stpeter at jabber.org
Thu Feb 12 11:14:18 CST 2004


On Thu, Feb 12, 2004 at 08:57:25AM -0800, LAPORTE,MARTIN (HP-Canada,ex1) wrote:
> Hello,
> 
> We have a corporate Jabber server (server "A"), running Jabber JCP V2.5.3 on
> RedHat 7.3.
> 
> I have a small server (server "B"), running jabberd 1.4.3 on RedHat 9.0, and
> also have installed mu-conference-0.6.0.  Everything runs smoothly when
> creating/joining rooms while logged in as a user of server "B".
> 
> My problem is that I am unable to create or join a room on server "B" when
> logged in with my account of server "A".  Here's the error I get when trying
> (I have changed the actual server names with "serverA" and "serverB"):
> 
> <presence from='test2 at conference.serverB' to='martin.laporte at serverA/Exodus'
> type='error'><priority>0</priority><error code='504'>Remote server timeout.
> Unable to deliver packet.</error></presence>
> 
> My questions are:
> 
> -          is it possible for the corporate server (server "A") to limit the
> creation of conference rooms to only server "A" (meaning if I am logged in
> as a user of server "A", I can only create rooms on server "A")?
> 
> -          or could it be that I need to turn a flag on server "B", enabling
> users from other servers to create conference rooms?

Hi Martin,

The most likely cause is that conference.serverB is set up in the config 
as conference.localhost, so that other servers can't resolve the domain.

/psa




More information about the JAdmin mailing list