Sweet, that gets me started. Now i have to dig though my notes to figure out how to get it so gaim and others default to use <a href="http://mud.domain.com">mud.domain.com</a> instead of <a href="http://conference.jabber.com">
conference.jabber.com</a>. I'm pretty sure i figured it out earlier.<br><br>Actually i found it right away.<br><br>ChildService <a href="http://muc.domain.com">muc.domain.com</a> Multi-user Conference Service<br><br>I added that just before before the Subdomain and psi was much happier. Gaim still defaulted to
<a href="http://conference.jabber.com">conference.jabber.com</a> or whatever.<br><br><div><span class="gmail_quote">On 7/23/07, <b class="gmail_sendername">Edward Rudd</b> <<a href="mailto:erudd@netfor.com">erudd@netfor.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Download mu-conference 0.7 from <a href="http://download.gna.org/mu-conference/">
http://download.gna.org/mu-conference/</a><br><br>I'm using the latest djabberd.. here is the relevant djabberd configuration<br><br><VHost mydomain><br> <Subdomain muc><br> <Plugin DJabberd::Component::External>
<br> ListenAddr <a href="http://127.0.0.1:5290">127.0.0.1:5290</a><br> Secret ConferenceSecret<br> </Plugin><br> </Subdomain><br><br> <Plugin DJabberd::Delivery::Local /><br> <Plugin DJabberd::Delivery::S2S />
<br></VHost><br><br>Build MUC by running "make" it will produce a mu-conference binary in<br>the src directory, copy it somewhere useful (ie /usr/local/bin)<br><br>copy the muc-default.xml to muc.xml (somewhere useful again, like /etc/muc)
<br><br>edit the muc.xml and change the <name> and <host> to be your MUC domain<br>and change the <port> to the port in djabberd (5290) and the <secret> to<br>the secret in djabberd.<br><br>Startup djabberd
<br>startup muc (mu-conference -c /path/to/muc.xml)<br><br>if you have logging on (and in debug), you should see djabberd showing<br>these lines<br><br>DEBUG DJabberd.Component.External Accepting connection from
<br>component <a href="http://muc.lan.netfor.com">muc.lan.netfor.com</a><br>DEBUG DJabberd.Connection.ComponentIn Making a<br>DJabberd::Connection::ComponentIn for fd 15<br>INFO DJabberd.Component.External Shutting down listener
<br>for component <a href="http://muc.lan.netfor.com">muc.lan.netfor.com</a><br>DEBUG DJabberd.Connection.ComponentIn Got stream start for<br>component <a href="http://muc.lan.netfor.com">muc.lan.netfor.com</a><br>
<br>That last one is important.. I wasn't getting that w/ muc 0.6. (so<br>nothing was working)<br><br>Gavin wrote:<br>> Oh, i've been meaning to try and figure this out. Can you share how you<br>> got everything working?
<br>><br>> On 7/23/07, *Edward Rudd* < <a href="mailto:erudd@netfor.com">erudd@netfor.com</a> <mailto:<a href="mailto:erudd@netfor.com">erudd@netfor.com</a>>><br>> wrote:<br>><br>> Ahah.. I got the subdomain version working now. I had to upgrade to
<br>> mu-conference 0.7 (released in june) and now it works like a charm.<br>><br>> Edward Rudd wrote:<br>> > The subdomain configuration does not work.<br>> ><br>> > All I get in the log is.
<br>> ><br>> > DEBUG DJabberd.Component.External Accepting<br>> connection from<br>> > component muc.mydomain<br>> > DEBUG DJabberd.Connection.ComponentIn Making a
<br>> > DJabberd::Connection::ComponentIn for fd 17<br>> > INFO DJabberd.Component.External Shutting down listener<br>> > for component muc.mydomain<br>> > DEBUG DJabberd.Delivery.LocalVHosts
mydomain -><br>> muc.mydomain<br>> > DEBUG DJabberd.Delivery.LocalVHosts muc.mydomain -><br>> mydomain<br>> > DEBUG DJabberd.Delivery.LocalVHosts mydomain ->
<br>> muc.mydomain<br>> > DEBUG DJabberd.Delivery.LocalVHosts muc.mydomain -><br>> mydomain<br>> ><br>> > (I'm using PSI client to join a groupchat). Everytime I attempt to
<br>> join<br>> > I get the 2 entries in the log (Dellivery.LocalVHosts) and an<br>> error back<br>> > to PSI.<br>> > Unable to join groupchat.<br>> > Reason:<br>> > (yeah that is no reason)
<br>> ><br>> > Martin Atkins wrote:<br>> >> Edward Rudd wrote:<br>> >>> I am trying to use the DJabberd::Component::External to have<br>> >>> mu-conference (
0.6.0 w/ JCR 0.2.4) connect into DJabberd.<br>> >>><br>> >>> I have tried all sorts of ways of configuring djabberd to get this<br>> >>> working but it never seems to work correctly.
<br>> >>><br>> >>> Here is the current setup.<br>> >>> <VHost muc.mydomain><br>> >>> <Plugin DJabberd::Component::External><br>> >>> ListenAddr
<a href="http://127.0.0.1:5290">127.0.0.1:5290</a> <<a href="http://127.0.0.1:5290">http://127.0.0.1:5290</a>><br>> >>> Secret Conferencing<br>> >>> </Plugin><br>> >>> </VHost>
<br>> >> I'm not sure if this is related to the problem, but assuming that<br>> you<br>> >> are using the same djabberd process for "mydomain" and "muc.mydomain"<br>
> >> you may like to use the subdomain idiom to avoid the need for<br>> djabberd<br>> >> to talk to itself over S2S:<br>> >><br>> >> <VHost mydomain><br>> >> # ....
<br>> >> <Subdomain muc><br>> >> <Plugin DJabberd::Component::External><br>> >> ListenAddr <a href="http://127.0.0.1:5290">127.0.0.1:5290</a> <<a href="http://127.0.0.1:5290">
http://127.0.0.1:5290</a>><br>> >> Secret Conferencing<br>> >> </Plugin><br>> >> </Subdomain><br>> >> </VHost><br>> >>
<br>> >> If you really do need to use S2S, make sure to include the<br>> following in<br>> >> your vhost configurations:<br>> >> S2S enable<br>> >> <Plugin DJabberd::Delivery::S2S />
<br>> >><br>> >> The S2S Delivery plugin must be declared after<br>> >> DJabberd::Component::External because it too is a delivery plugin.<br>> >><br>><br>><br><br>
</blockquote></div><br>