[jadmin] Re: Cannot run MU-conference with Jabberd2

[Matthias Wimmer]

Hi Alexander!

Alexander Semyonov schrieb:
> Hi! Sure, c2s is listening on port 5222 and 5223 (for secure
> connections). This is configured in "local" section of c2s.xml. But
> "router" section is not the same. Here are "router" and "local" sections
> of c2s.xml. If I change port number in "router" section I can't even
> connect. So, we have "router" section in c2s.xml and "local" section in
> router.xml; it means that roster module is configured in two files
> twice. Why? :-O
> 
> <router>
>     <!-- IP/port the router is waiting for connections on -->
>     <ip>127.0.0.1</ip>            <!-- default: 127.0.0.1 -->
>     <port>5347</port>             <!-- default: 5347 -->
> </router>

The router section has nothing to do with the handling of the roster. 
The router section configures the "interconnection" between the 
different jabberd2 processes. Therefore the router section has to have 
the same settings in all configuration files of jabberd2.


Tot kijk
     Matthias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4263 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/jadmin/attachments/20060825/7b78620a/smime-0004.bin