component::external configuration?

Gavin halkeye at gmail.com
Tue Jul 24 00:42:23 UTC 2007


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 mud.domain.com instead of
conference.jabber.com. I'm pretty sure i figured it out earlier.

Actually i found it right away.

ChildService muc.domain.com Multi-user Conference Service

I added that just before before the Subdomain and psi was much happier. Gaim
still defaulted to conference.jabber.com or whatever.

On 7/23/07, Edward Rudd <erudd at netfor.com> wrote:
>
> Download mu-conference 0.7 from http://download.gna.org/mu-conference/
>
> I'm using the latest djabberd.. here is the relevant djabberd
> configuration
>
> <VHost mydomain>
>   <Subdomain muc>
>     <Plugin DJabberd::Component::External>
>       ListenAddr 127.0.0.1:5290
>       Secret ConferenceSecret
>     </Plugin>
>   </Subdomain>
>
>   <Plugin DJabberd::Delivery::Local />
>   <Plugin DJabberd::Delivery::S2S />
> </VHost>
>
> Build MUC by running "make" it will produce a mu-conference binary in
> the src directory, copy it somewhere useful (ie /usr/local/bin)
>
> copy the muc-default.xml to muc.xml (somewhere useful again, like
> /etc/muc)
>
> edit the muc.xml and change the <name> and <host> to be your MUC domain
> and change the <port> to the port in djabberd (5290) and the <secret> to
> the secret in djabberd.
>
> Startup djabberd
> startup muc  (mu-conference -c /path/to/muc.xml)
>
> if you have logging on (and in debug), you should see djabberd showing
> these lines
>
> DEBUG DJabberd.Component.External              Accepting connection from
> component muc.lan.netfor.com
> DEBUG DJabberd.Connection.ComponentIn          Making a
> DJabberd::Connection::ComponentIn for fd 15
> INFO  DJabberd.Component.External              Shutting down listener
> for component muc.lan.netfor.com
> DEBUG DJabberd.Connection.ComponentIn          Got stream start for
> component muc.lan.netfor.com
>
> That last one is important.. I wasn't getting that w/ muc 0.6. (so
> nothing was working)
>
> Gavin wrote:
> > Oh, i've been meaning to try and figure this out. Can you share how you
> > got everything working?
> >
> > On 7/23/07, *Edward Rudd* < erudd at netfor.com <mailto:erudd at netfor.com>>
> > wrote:
> >
> >     Ahah.. I got the subdomain version working now.  I had to upgrade to
> >     mu-conference 0.7 (released in june) and now it works like a charm.
> >
> >     Edward Rudd wrote:
> >     > The subdomain configuration does not work.
> >     >
> >     > All I get in the log is.
> >     >
> >     > DEBUG DJabberd.Component.External               Accepting
> >     connection from
> >     > component muc.mydomain
> >     > DEBUG DJabberd.Connection.ComponentIn          Making a
> >     > DJabberd::Connection::ComponentIn for fd 17
> >     > INFO  DJabberd.Component.External               Shutting down
> listener
> >     > for component muc.mydomain
> >     > DEBUG DJabberd.Delivery.LocalVHosts            mydomain ->
> >     muc.mydomain
> >     > DEBUG DJabberd.Delivery.LocalVHosts            muc.mydomain ->
> >     mydomain
> >     > DEBUG DJabberd.Delivery.LocalVHosts            mydomain ->
> >     muc.mydomain
> >     > DEBUG DJabberd.Delivery.LocalVHosts            muc.mydomain ->
> >     mydomain
> >     >
> >     > (I'm using PSI client to join a groupchat). Everytime I attempt to
> >     join
> >     > I get the 2 entries in the log (Dellivery.LocalVHosts) and an
> >     error back
> >     > to PSI.
> >     >   Unable to join groupchat.
> >     >   Reason:
> >     > (yeah that is no reason)
> >     >
> >     > Martin Atkins wrote:
> >     >> Edward Rudd wrote:
> >     >>> I am trying to use the DJabberd::Component::External to have
> >     >>> mu-conference (0.6.0 w/ JCR 0.2.4) connect into DJabberd.
> >     >>>
> >     >>> I have tried all sorts of ways of configuring djabberd to get
> this
> >     >>> working but it never seems to work correctly.
> >     >>>
> >     >>> Here is the current setup.
> >     >>> <VHost muc.mydomain>
> >     >>>     <Plugin DJabberd::Component::External>
> >     >>>       ListenAddr 127.0.0.1:5290 <http://127.0.0.1:5290>
> >     >>>       Secret Conferencing
> >     >>>     </Plugin>
> >     >>> </VHost>
> >     >> I'm not sure if this is related to the problem, but assuming that
> >     you
> >     >> are using the same djabberd process for "mydomain" and "
> muc.mydomain"
> >     >> you may like to use the subdomain idiom to avoid the need for
> >     djabberd
> >     >> to talk to itself over S2S:
> >     >>
> >     >> <VHost mydomain>
> >     >>     # ....
> >     >>     <Subdomain muc>
> >     >>        <Plugin DJabberd::Component::External>
> >     >>            ListenAddr 127.0.0.1:5290 <http://127.0.0.1:5290>
> >     >>            Secret Conferencing
> >     >>        </Plugin>
> >     >>     </Subdomain>
> >     >> </VHost>
> >     >>
> >     >> If you really do need to use S2S, make sure to include the
> >     following in
> >     >> your vhost configurations:
> >     >> S2S enable
> >     >> <Plugin DJabberd::Delivery::S2S   />
> >     >>
> >     >> The S2S Delivery plugin must be declared after
> >     >> DJabberd::Component::External because it too is a delivery
> plugin.
> >     >>
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/djabberd/attachments/20070723/f0d9842c/attachment.html


More information about the Djabberd mailing list