[jadmin] Conference setup docs

Wilfried Maschtera wilfried.maschtera at maschtera.at
Sun Nov 12 04:02:32 CST 2006


>From my experience:

- make sure that all pid files are deleted before 
  restarting jabber.
- check whether in router.xml 
  <alias name='id of your server' is active.
  "id of your server" is in sm.xml and should also be
  the realm in c2s.xml. If yes
  router will fail. You can see it if you start the
  components with -D. The router complains, that
  "id of your server" is already aliased. This sounds 
  strange but I suppose there is no other way to xfer
  the clients input to a chat room to mu-conference.
- the host name in mu-...xml must not be the same as the
  "id of your server". Choose a different one (dsn
  resolveable, in your case pointing to the "id of your
  server") and insert an alias in router.xml.
  E.g
  mu-c...xml:
  <name>anyname</name>
  <host>name_of_conference_server</host>

  route.xmxl:
  <alias name=' me_of_conference_server' target='anyname'/>

Kind regards, Wilfried Maschtera

  
On Sat, Nov 11, 2006 at 03:12:46PM -0500, Robert Fitzpatrick wrote:
> On Sat, 2006-11-11 at 19:25 +0100, Wilfried Maschtera wrote:
> > Is it equivalent to jabber2 and mu-conference? 
> > 
> 
> Yes, actually, since posting my question yesterday, I found jabberd2 in
> the FreeBSD ports system and instead, removed 1.4 and jabber-conference,
> then installed jabberd-2.0.11_2 and mu-conference. I have IM working
> again with this version using LDAP auth and PostgreSQL storage. Although
> still an issue with the conferencing, this error started popping up
> whenever I restart (or stop) the jabberd server:
> 
> esmtp# rc.d/jabberd restart
> Stopping jabberd.
> ERROR: router died.  Shutting down server.
> Starting jabberd.
> 
> Sometimes it says c2s died or resolver died, but everything seems to run
> fine. But still not sure about how to get conferencing to work. I have
> mu-conference starting fine, but cannot find any rooms when searching. I
> have my /usr/local/etc/muc.xml setup now like this:
> 
>   <name>muclinker</name>
>   <host>conference.domain.tld</host>
>   <ip>127.0.0.1</ip>
>   <port>5347</port>
>   <secret>pek2jg2n</secret>
> 
>   <spool>/var/jabberd/spool/conference.domain.tld</spool>
>   <logdir>/var/jabberd/log</logdir>
>   <pidfile>/var/jabberd/pid/mu-conference.pid</pidfile>
>   <!--
>      <logstderr/>
>   -->
>   <loglevel>124</loglevel>
>     <conference xmlns="jabber:config:conference">
>       <public/>
>       <vCard>
>         <FN>Public Chatrooms</FN>
>         <DESC>This service is for public chatrooms.</DESC>
>         <URL>http://domain.tld/</URL>
>       </vCard>
>       <history>40</history>
>       <logdir>/var/jabberd/log/</logdir>
>       <notice>
>         <join>has become available</join>
>         <leave>has left</leave>
>         <rename>is now known as</rename>
>       </notice>
>       <sadmin>
>         <user>presence at domain.tld</user>
>       </sadmin>
>       <room jid="help at conference.domain.tld">
>         <name>Assistance Zone</name>
>         <privacy/>
>       </room>
>       <room jid="admin at conference.domain.tld">
>         <name>Admin only</name>
>         <secret>test</secret>
>         <notice>
>           <join> just rocks!</join>
>           <leave> gets lost</leave>
>           <rename> feels it is more important to be known as </rename>
>         </notice>
>       </room>
>     </conference>
> 
> Then in my /usr/local/etc/jabberd/router.xml, my alias section is setup
> like this:
> 
>   <aliases>
>     <alias name='conference.domain.tld' target='muclinker'/>
>   </aliases>
> 
> Thanks for the help!
> 
> -- 
> Robert
> 
> _______________________________________________
> JAdmin mailing list
> JAdmin at jabber.org
> http://mail.jabber.org/mailman/listinfo/jadmin
> FAQ: http://www.jabber.org/about/jadminfaq.shtml
> _______________________________________________



More information about the JAdmin mailing list