On Mon, Dec 10, 2001 at 07:36:04AM +0100, Bjorn Wesen wrote:
> Just FYI this error occurs when the latest licq cvs tries to send a msg to 
> an icq 2001b user:
> 
> 00:22:01: [TCP] Connecting to winclient (xxxxxx) at aaa.bbb.ccc.ddd:8729.
> 00:22:01: [TCP] Shaking hands with winclient (xxxxxx) [v6].
> 00:22:01: [WRN] Handshake error, remote side closed connection.
> 
> also, if the icq2001b client initiates the connection, licq gets the 
> message but still cant send anything back over the connection. at least 
> that part worked with licq-1.0.3.
No, it didn't. 1.0.3's behaviour was exactly the same.
Dirk posted something about a fix on Nov 14th. I'm not shure, but I think he simply 
disabled CPacketTcp::PostBuffer_v6. The latest CVS version no longer contains that 
patch. Maybe he only fixed it in HEAD and not in V8_BRANCH.

> sending through the server seems to work in many cases but sometimes 
> messages are lost,
I only experience lost messages with v8 when I send messages to offline users.
ICQ 2001b can send to offline users. When licq sends to an offline user, it receives a 
family 4/subtype 1 packet but when ICQ 2001b sends to an offline user, it receives a 
family 4/subtype 12 packet. I guess it has to do with the capabilities we send to the 
server.

> the same happens to incoming messages, some are magically lost (but that seems to 
>happen mostly from icq99b users..)
ICQ 99b uses the same UDP protocol licq-1.0.3 used, so it's not licq's "fault".

  Daniel


_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel

Reply via email to