Followup on message delivery issue

[birox]

I was thinking that your otr fix would fix the issue. But it hasn't.
I had 2 users in different browser sessions communication to each other with no issue. Then I logged in with one of them on jitsi desktop app while also on the web jsxc/strophe client. I sent a message from the jitsi desktop client to the other user, the user received the message and when replied only jitsi desktop received the message, not jsxc. And since that test the user that was logged in to jitsi is not receiving messages anymore from the user that hat an open session with this user on jitsi. Thinking about it, all users i had issues with used some sort of other client, desktop or mobile like ChatSecure.

So something is happening when a webclient user interacts with a otherclient user. If the otherclient user logs to webclient he does not receive messages from the webclient user that interacted with on otherclient.

[sualko]

I think thats no bug, it is a feature of xmpp. But only to get it right, you have 2 users (A and B). A is online in two different clients (A/Jitsi and A/jsxc) and user B is only online in jsxc. Now if A/Jitsi writes a message to B, A/jsxc didn't receive a message? If thats the case everything works as expected, because only the user with the highest state or priority gets a message by default (serverside). But should a client receive a message from a client with lower priority, he will continue the conversation with that resource.

[birox]

Well that's the problem client A/jsxc never receives any message from B after A/jitsi and B communicated, Not even if A/jitsi session is closed...

[sualko]

Can you confirm, that this problem only occurs, if you use OTR? Because if you receive an unrecognized otr message the default otr behavior is to ignore this message. I did some enhancement in the otr error handling and enabled the otr debugging mode to inform the discussion partner. I will build a new alpha if I get response to my ticket arlolra/otr#45.

[sualko]

I leave this ticket open, because I have to test more on this issue.

[birox]

Ok, i will be testing further to, thank you