You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
gentoo-overlay/net-im/mu-conference/files
root d9d99d08d3
Automatic update [Wed Nov 9 11:33:18 MSK 2011].
13 years ago
..
README.Gentoo Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago
mu-conference-0.7.init Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago
mu-conference-conf.d Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago
mu-conference-makefile.patch Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago
muc-transport.init Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago
muc-transport.init-r2 Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago
muctrans.xml Automatic update [Wed Nov 9 11:33:18 MSK 2011]. 13 years ago

README.Gentoo

This is a small help to get you started with the MSN Jabberd transport in 

Gentoo.

Edit /etc/jabber/muctrans.xml . This is the config file for MU-Conference.
There change all references to localhost with the FQDN (Fully Qualified Domain
Name) for your server.

In the msnlinker section enter the IP of your main jabber server (normally
127.0.0.1) and choose a port and secret (secret is the password the MSN
transport will use to connect to the main jabber server).

Now back to the multiple.xml to tell your main jabber server to listen to
connections from the MU transport.
Search for "<vcard2jud/>" and after that, and before the </jsm> add:

<browse>
<item category="conference" type="public" jid="conference.localhost" name="Public Conferencing" version="0.6.0">
<ns>http://jabber.org/protocol/muc</ns>
</item>
</browse>

Again here change localhost for your FQDN.

Scrool down to the bottom of the file, and just before the </jabber> add:

<service id="muclinker">
<host>conference.localhost</host>
<accept>
<ip>127.0.0.1</ip>
<port>31518</port>
<secret>mymucsecret</secret>
</accept>
</service>
(By know you know you have to change localhost for you FQDN).
One very importante thing: even if it is the same machine the name's for the
various services must be diferent, that means that there must be valid aliases
for conference.FQDN .

If you need help with configuration you can try the Jabber Admin Mailling list:
http://mailman.jabber.org/listinfo/jadmin