[jdev] s2s on jabberd 1.4.4 (jabberd14)

[Peter Schwindt]

Paul,

2006/3/21, Paul C. <PaulC at car-part.com>:

> I'm not sure why it isn't working.   Here is what I did in the
> jabber.xml file for s2s (jabber.domain.com is a FQDN):

>  <service id="s2slinker">
> <host>jabber.domain.com</host>
>    <accept>
>      <ip>127.0.0.1</ip>
>      <port>31519</port>
>      <secret>secret</secret>
>    </accept>
>  </service>

That looks ok so far, but I use a different host for each of the the
s2s processes,
something like s2s.jabber.domain.com, s2s-2, ...

> been working for a while) and then I load up my s2s.xml.  the s2s.xml
> looks like this:
> <jabber>
>  <service id="s2slinker">
>    <uplink/>
>    <connect>
>      <ip>127.0.0.1</ip>
>      <port>31519</port>
>      <secret>secret</secret>
>    </connect>
>        </service>


> <service id="s2s">

This one is wrong. Please use the upper mentioned host-definition here.

>    <load>
>      <dialback>/opt/jabberd/dialback/libjabberddialback.so</dialback>
>    </load>
>    <dialback xmlns='jabber:config:dialback'>
>      <legacy/>
>      <ip port="5269"/>
>     <karma>
>      <heartbeat>2</heartbeat>
>      <init>74</init>
>      <max>94</max>
>      <inc>6</inc>
>      <dec>0</dec>
>      <penalty>-1</penalty>
>      <restore>84</restore>
>    </karma>
> </dialback>
>  </service>
>  <pidfile>./s2s.pid</pidfile>
> </jabber>

Looks so far. But you don't use ssl? ;-)

Peter

--
xmpp:vt100 at jabber.ccc.de