Hi,<br>
<br>
I'm reasonably sure our server is ok, because I just tried the same conversation between<br>
Miranda and Exodus on the same server. The xml I catch from client2 is:<br>
<br>
RECV: <message to="<a href="http://roel@davenport.office.sping.nl/BuzzaaMobile">roel@davenport.office.sping.nl/BuzzaaMobile</a>"
type="chat" id="mir_8"
from="<a href="http://roel@davenport.office.sping.nl/buzzaaclient"">roel@davenport.office.sping.nl/buzzaaclient"</a>><body>test</body><x
xmlns="jabber:x:event"><composing/></x></message><br>
SENT: <message id="jcl_28"
to="<a href="http://roel@davenport.office.sping.nl/buzzaaclient">roel@davenport.office.sping.nl/buzzaaclient</a>"
type="chat"><thread>6831ae16f80f18d1218cc66d2d43d9409ba0c15f</thread><body>reply3</body><x
xmlns="jabber:x:event"><composing/></x></message><br>
<br>
And all goes as expected....<br>
<br>
Roel<br>
<br>
ps. Oh well, if everything fails, I can always blame my xmpp library...agsXMPP.... ;)<br><br><div><span class="gmail_quote">On 11/10/05, <b class="gmail_sendername">Alexander Gnauck</b> <<a href="mailto:gnauck@ag-software.de">
gnauck@ag-software.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">hi Roel,<br><br>your XML looks correct to me. I looks like there is a routing problem in
<br>the server. Did you try your clients with another public server?<br><br>Regards<br>Alex<br><br><br>Roel Spruit schrieb:<br>> This is the xml from both client1 and client2, I censured all jids and<br>> stuff.<br>
><br>> CLIENT1:<br>> SENT: <message xmlns="jabber:client" to="<a href="http://roel@blah.nl/client2">roel@blah.nl/client2</a><br>> <<a href="http://roel@blah.nl/client2">http://roel@blah.nl/client2
</a>>"<br>> type="chat"><body>sometext</body><thread>blah</thread></message><br>><br>> CLIENT2<br>> RECV: <message to="<a href="http://roel@blah.nl/client2">
roel@blah.nl/client2</a> <<a href="http://roel@blah.nl/client2">http://roel@blah.nl/client2</a>>"<br>> type="chat" from="<a href="http://roel@blah.nl/client1">roel@blah.nl/client1</a>"<br>
> <<a href="http://roel@blah.nl/client1"">http://roel@blah.nl/client1"</a>>><body>sometext</body><thread>blah</thread></message><br>> SENT: <message id="jcl_9" to="
<a href="http://roel@blah.nl/client1">roel@blah.nl/client1</a><br>> <<a href="http://roel@blah.nl/client1">http://roel@blah.nl/client1</a>>"<br>> type="chat"><thread>blah</thread><body>heyyy</body><x
<br>> xmlns="jabber:x:event"><composing/></x></message><br>> RECV: <message id="jcl_9" to="<a href="http://roel@blah.nl/client1">roel@blah.nl/client1</a><br>> <
<a href="http://roel@blah.nl/client1">http://roel@blah.nl/client1</a>>" type="chat" from="<a href="http://roel@blah.nl/client2"">roel@blah.nl/client2"</a><br>> <<a href="http://roel@blah.nl/client2"">
http://roel@blah.nl/client2"</a>>><thread>blah</thread><body>somereply</body><x<br>> xmlns="jabber:x:event"><composing/></x></message><br>><br>> We are using the Jive jabber server
<br>><br>> Thanks in advance!<br>><br>> Roel<br>> On 11/10/05, *Matthias Wimmer* <<a href="mailto:m@tthias.net">m@tthias.net</a> <mailto:<a href="mailto:m@tthias.net">m@tthias.net</a>>> wrote:<br>
><br>> Hi Roel!<br>><br>> I propose you send us a dump of the messages, so we can check why it is<br>> routed that we. It might also be interesting which server software you<br>> are using, in case that there is a bug in the server.
<br>><br>><br>> Tot kijk<br>> Matthias<br>><br>> Roel Spruit schrieb:<br>><br>> > Hi Folks,<br>> ><br>> > I'm developing a limited xmpp client that is meant to communicate
<br>> with<br>> > another<br>> > xmpp client...that I'm also building (yeah, busy busy). These two<br>> > clients will<br>> > be logged on at the same jabber server, under the same name, but each
<br>> > under<br>> > a different resource.<br>> ><br>> > My problem: I can send a message from client1 to client2, and it<br>> > arrives as expected,<br>> > with the client1 resourcename as the sender. However, when I reply to
<br>> > this message,<br>> > the reply ALSO arrives at client2, and not at client1.<br>> ><br>> > I figured this was a priority problem, but it doesn't seem to be,<br>> with
<br>> > client1 at the maximum<br>> > priority it still fails.<br>> ><br>> > Can anybody help me with this problem?<br>> ><br>> > Regards,<br>> >
<br>> > Roel Spruit<br>><br>><br>><br><br></blockquote></div><br>