Thanks aznidin, im trying to sort out ( curious ) how the server 2 server protocol really works… in my tests i found another problem, this one is really uggly:
OFFLINE messages do not work if:
user_a (at server1)
user_ b (at server2)
sends msg to b
SAVES OFFLINE MSGs IN SERVER2! (in remote server?..hum…)
sends msg to b
DOES NOT SAVE OFFLINE MSGs! (because he tries to send them to de server2)
users from remote server dont receive OFFLINE msgs if the remote server is DOWN …but the user that sends them is able to send them!!!
Messages are lost if one of the servers goes down!..It depends if i am writing to a user offline on a remote server or local server
Am i missing something? If its not a bug …well…i am expecting receive offline msgs… i configured servers to do so!
This s2s protocol seams very very limited…it exchanges presences…nothing more…the rest is done by the local server…look at the example of the rosters…i never receive the names from users from remote server because the local server takes care of it , sending this to me:
<packet xmlns=“http://www.jivesoftware.org” streamID=“7c02db2” status=“auth” timestamp=“Oct 1, 2007 2:56:22 PM”>
<iq xmlns="" type=“result” id=“Jeti_0.5135971622230516_2” to=“email@example.com/JETI”>
<item jid="firstname.lastname@example.org" name="email@example.com" subscription=“both”>
This is a response from local server to a query for roster…he assumes NAME = JID as you can see …he does not comunicate with the remote server in this situation!
does not make much sense