Looking at the XML returned by ejabberd when attempting to create a conference room, I see "Conference room does not exist".
The Jabber client lets me type in a message to the conference room but then responds with "Your message to the room bounced."
I've verified I'm an administrator by running the web administration face at 5280 and looking at the admin list.
I'm running:
Exodus 0.9.1
ejabberd 0.9.1
Freebsd 4.10.0
--- A little later:
The create a room dialogue came up after several minutes waiting. I checked some boxes (such as to make it permanent) and submitted it. It then seemed to create the conference room. Sending a message echoed it back, and I was showing up on the roster for the room
--- Later still:
I temporarily lost my connection. Upon reestablishing connection and relogging onto ejabberd I again tried to send a message but this time I received (in the XML debug window as usual): "Only occupants are allowed to send messages to the conference". Leaving and reentering the conference didn't help.
I then exited again, and this time when joining a conference I chose to browse servers for conference rooms. It showed 2 rooms, both named the same but one of them had "(0)" after the server JID. I chose that one, and it worked. Leaving it again, I then tried to browse again but this time there was only the "(0)" conference room -- and it worked.
1. Which Jabber-client do
1. Which Jabber-client do you use? There is no such notion as "Create conference room". It is created when someone is joining it.
2. When you lost connection, ejabberd disconnects you from the room. After reconnect you have to join the room again.
3. It seems that browsing issues are client issues.