[jdev] s2s on jabberd 1.4.4 (jabberd14)

[Paul C.]

I tried posting this to the Jadmin list, and didn't get a response.  
Peter Saint-Andre suggested that this list may be more helpful.  We have 
six+ jabberd 1.4.4 servers running on Solaris 9.  A couple of times a 
week, the service has to be restarted because the dns resolver or s2s 
stops working properly.  So, Matthias suggested that our company could 
run s2s in its own process and the s2s process could be restarted 
instead of the entire service.  I have tried to get this working, basing 
my work on the way we have MUC running in its own process.  Here is my 
previous email to the jadmin list:
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>
and I started the main jabberd process with this:
jabberd -U jabber -c /opt/jabber/config/jabber.xml -H /opt/jabber -B

Then I load up the muc which uses a muclinker (i know this works...its 
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">
   <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>

The errors I am getting in the error log are:
20060119T16:20:27: [notice] (s2s): bouncing a routed packet to s2s from 
(null): Internal Delivery Error
20060119T16:20:27: [warn] (s2s): dropping a routed packet to s2s from 
s2s: Internal Delivery Error
20060119T16:20:33: [notice] (s2s): bouncing a routed packet to s2s from 
(null): Internal Delivery Error
20060119T16:20:33: [warn] (s2s): dropping a routed packet to s2s from 
s2s: Internal Delivery Error

A netstat -a shows that it is listening on localhost for 31519 and on * 
for 5269.  What did I configure incorrectly? OR can someone post an 
example they have of this service running by itself?  Point me to some 
other documentation about this?  Like I said, I've tried the jadmin list 
and I've tried to contact Matthias as well.

Thanks
Paul