Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I wish to set up a spare muc service on our non-primary ejabberd node so that users can continue to use muc in a limited fashion when our primary ejabberd node (which hosts the primary muc service) is down for maintenance.

Here is the configuration that I am using, which seems to work.

  {mod_muc,      [
                  {host, "spare_conference.@HOST@"},
                  {access, muc},
                  {access_create, muc},
                  {access_persistent, muc_admin},
                  {access_admin, muc_admin}

However, it shows up in service discovery with the same name as the other muc service: "Chatrooms".

The iq stanza from the server has:

identity category="conference" type="text" name="Chatrooms"

Is that "name" attribute configurable? I don't see this in the ejabberd guide documentation. How do I configure the muc service so that it shows a different name?

share|improve this question

You can't change the the name without recompiling the code. It's hardcoded in src/mod_muc/mod_muc.erl

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.