ejabberd: shared lists

Previous notes on setting up ejabberd 1 , 2 and 3 .

ejabberd allows you to create pre-prepared contact lists that are available to certain groups of users. Since our server is configured for corporate needs, this would be useful. A new person arrives, connects to the server, and he already has everything in his contact list that he may need, and grouped by department.


To make such predefined lists, you need to connect the mod_shared_roster module:

 {modules, [
     {mod_shared_roster, [}
 ]}.

General lists are configured only via the web interface:

  http://company.ru:5280/admin/ 

Next in the menu, select: Virtual hosts - company.ru - General Contacts
')
Enter the name of the group to display in the web interface. For example, "admins" and click add. In the same way we add groups for other departments.


Now we go to any of the groups we have created and start filling it out.

Title

The name of the group that will be displayed in the jabber client’s contact list.

Description

As written in the mod_shared_roster documentation, this value does not affect anything.

The members

List of contacts that should be displayed in this group. Each JID is indicated on a new line. You can specify contacts from any domains, and not just from the one for which the roster is configured.

Visible groups

List of groups that will be displayed for the group being edited. That is, if we are editing the PHP group now, then this list should list the groups that should be displayed for the contacts listed in the “Members” column. The name given to the group when it is created is indicated as the name of the group.

After completing the configuration, clients must reconnect to receive these changes.

In conjunction with LDAP, the right clients (such as MDC ) show the person's first and last name. Psi and SIM for me showed only JID, and even kept this display in my roster.

Now each of our employees has contacts of all other employees. It remains only to knock ...