Looking for ejabberd docs?

To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »

MUC invite/persistence problem

Submitted by horlix on Thu, 2005-04-07 11:54

Hi All,

I have ejabberd 0.7.5 running on Freebsd 4.10 in a corporate environment. All clients are using Exodus v9.0.0 on Windows NT4 SP6.

I must say that its far superior to any messaging system we have used in the past and my recent discovery of pushroster.erl has been an absolute godsend! Thanks!

The only problem I have currently is with the configuration of MUC rooms. I currently have mod_muc configured to allow all permissions to everyone but we dont seem to be able to make rooms persistent or invite users into a MUC. The only errors displayed anywhere are when an invite fails, the person doing the inviting receives the text "ERROR: " in their MUC window, the person being invited receives nothing at all. When the last person leaves the MUC the room is destroyed. No errors are displayed in the erlang console or logs at any point.

I believe Exodus to be a MUC enabled jabber client but am restricted as to what other clients I can try due to the rather old OS we are running. I may try Pandion today when I get into the office.

Does this sound like a client or server config problem? I can post details from ejabberd.cfg on request when I get into the office later.

Thanks for any help in advance.

try exodus 0.9.1.0

Submitted by mfoss on Thu, 2005-04-07 21:34.

Exodus 0.9.0.0 is really old. Try the recently released 0.9.1.0.

If that does not help, paste here the part of 'modules' in your ejabberd.cfg about mod_muc.

thanks

Submitted by horlix on Thu, 2005-04-07 22:55.

Hi badlop,

Thanks for the suggestion, I've installed Exodus 0.9.1.0 on one client machine and logged into an admin account and there was no change unfortunately. Here are the relevant parts of ejabberd.cfg as requested :-

{access, muc_admin, [{allow, admin}]}.
{access, muc, [{allow, all}]}.

% Default options for mod_muc:
% host: "conference." ++ ?MYNAME
% access: all
% access_create: all
% access_admin: none (only room creator has owner privileges)
{mod_muc, [{access, muc},
           {access_create, muc},
           {access_admin, muc_admin}]},

Thanks for any further suggestions, I'm sure its something stupid I'm missing in the cfg.

the config seems ok

Submitted by mfoss on Sat, 2005-04-09 10:17.

I'm sure its something stupid I'm missing in the cfg

That config seems ok to me, so:

Try with other MUC capable clients (Pandion, Tkabber, Gaim) to make sure it isn't an Exodus bug.
Compare your whole ejabberd.cfg with the template one, and the ejabberd log file, to make sure the rest of the config is correct.

we don't seem to be able to m

Submitted by mfoss on Sat, 2005-04-09 10:16.

we don't seem to be able to make rooms persistent

How do you check if a room is really persistent or not?

or invite users into a MUC.

'Send invitation' is a privilege. Only the room owner and admins can send it, but you can configure the room to allow participants to send invitations.