hi Roel,

your XML looks correct to me. I looks like there is a routing problem in the server. Did you try your clients with another public server?

Regards
Alex


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">><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">><thread>blah</thread><body>somereply</body><x xmlns="jabber:x:event"><composing/></x></message>

We are using the Jive jabber server

Thanks in advance!

Roel
On 11/10/05, *Matthias Wimmer* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> 
wrote:

    Hi Roel!

    I propose you send us a dump of the messages, so we can check why it is
    routed that we. It might also be interesting which server software you
    are using, in case that there is a bug in the server.


    Tot kijk
         Matthias

    Roel Spruit schrieb:

     > Hi Folks,
     >
     > I'm developing a limited xmpp client that is meant to communicate
    with
     > another
     > xmpp client...that I'm also building (yeah, busy busy). These two
     > clients will
     > be logged on at the same jabber server, under the same name, but each
     > under
     > a different resource.
     >
     > My problem: I can send a message from client1 to client2, and it
     > arrives as expected,
     > with the client1 resourcename as the sender. However, when I reply to
     > this message,
     > the reply ALSO arrives at client2, and not at client1.
     >
     > I figured this was a priority problem, but it doesn't seem to be,
    with
     > client1 at the maximum
     > priority it still fails.
     >
     > Can anybody help me with this problem?
     >
     > Regards,
     >
     > Roel Spruit




Reply via email to