[JDEV] ICQ transport question
roju at home.com
Wed Oct 24 23:17:20 CDT 2001
I've been subsciber to an icq-devel mailing list for the last while, and
they've reported that for old ICQ protocol versions (ie, 5 and under), the
servers have been dropping random offline messages. I assume the transport
uses server messages, so that's probably where the problem lies. I also
assume that the transport is probably version 5.
Apparently version 7 also had this problem, but less so. Also, the official
clients tend to use client-client, bypassing any server trouble.
>From what I hear, the problem has cleared up now, but I'm not sure if that's
Hopefully this helps,
> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On
> Behalf Of Guy Segal
> Sent: October 24, 2001 11:34 AM
> To: jdev at jabber.org
> Subject: [JDEV] ICQ transport question
> Hello all,
> I have an up and running Jabber server (version 1.4.1) with an
> ICQ transport
> All is well, except that only 80 percent of ICQ messages actually
> arrive to
> their destination.
> I've studied the ICQ transport log file, and saw there's a packet
> number for
> outgoing packets: server write 0144.
> I've also noticed all these packets either receive an acknowledgement from
> the Mirabilis ICQ server: server acked 0144,
> or get discarded after a number of unsuccessful attempts.
> I thought the ICQ messages that were allegedly sent but never
> arrived might
> be packets that were discarded, but that is NOT the case!
> All packets which never arrived were acknowledged as received by the ICQ
> How can I know the actual status of an ICQ message I send? Why is
> the Jabber
> system much less reliable than an actaul ICQ client?
> Guy Segal
> Software Engineer
> Email : segal at telemessage.com
> Phone : (+972) 3 9225252 Ext. 934
> Mobile : (+972) 53 411723
> Web : www.telemessage.com
> jdev mailing list
> jdev at jabber.org
More information about the JDev