Hi Roel!
Roel Spruit schrieb:
This is the xml from both client1 and client2, I censured all jids and
stuff.
CLIENT1:
SENT: <message xmlns="jabber:client" to="[EMAIL PROTECTED]/client2
<http://[EMAIL PROTECTED]/client2>"
type="chat"><body>sometext</body><thread>blah</thread></message>
CLIENT2
RECV: <message to="[EMAIL PROTECTED]/client2 <http://[EMAIL PROTECTED]/client2>"
type="chat" from="[EMAIL PROTECTED]/client1"
<http://[EMAIL PROTECTED]/client1%22>><body>sometext</body><thread>blah</thread></message>
SENT: <message id="jcl_9" to="[EMAIL PROTECTED]/client1
<http://[EMAIL PROTECTED]/client1>"
type="chat"><thread>blah</thread><body>heyyy</body><x
xmlns="jabber:x:event"><composing/></x></message>
RECV: <message id="jcl_9" to="[EMAIL PROTECTED]/client1
<http://[EMAIL PROTECTED]/client1>" type="chat" from="[EMAIL PROTECTED]/client2"
<http://[EMAIL PROTECTED]/client2%22>><thread>blah</thread><body>somereply</body><x
xmlns="jabber:x:event"><composing/></x></message>
Have you checked that both clients have sent <presence/> to the server?
Does the presence have non-negative priority? (Well resource-directed
messages should be sent to the correct session anyway, but maybe that's
the difference to your tests with Exodus, that worked.
Like Alexander said: The <message/>s look correct. There should be
either the session not correctly set up (no <presence/> sent), or maybe
a server but only affecting sessions in some conditions.
Tot kijk
Matthias
