Hey,
since upgrading to IM Transport v.1.1.0 we experience even more problems with icq transport than ever before:
1) in most instances the transport apparently couldn’t connect to icq, the transport-icon in roster stay’s “offline”. a short look at openfire-logs revealed no errors, no warnings, and the following messages in debug:
2007.08.13 13:57:44 A new session has come online: user@jabberserver.de/Psi
2007.08.13 13:57:44 Created icq session for user@jabberserver.de/Psi as ‘000_ICQ_NR_000’
2007.08.13 13:57:44 OSCAR login service state change from NOT_CONNECTED to INITING
2007.08.13 13:57:44 Received presence packet:
2007.08.13 13:57:44 icq: Sending packet:
2007.08.13 13:57:44 OSCAR login service state change from INITING to RESOLVING
2007.08.13 13:57:44 OSCAR login service state change from RESOLVING to CONNECTING
2007.08.13 13:57:44 Connect Socket[http://addr=/85.10.193.115,port=44595,localport=5269|http://addr=/85.10.193.115, port=44595,localport=5269]
2007.08.13 13:57:44 OSCAR login service state change from CONNECTING to CONNECTED
Even though OSCAR obviously connects successful to the icq login server, the status in contact-list is not refreshed and online-buddies are not shown. Later debug messages shows some activity, but nothing is postulated to roster:
2007.08.13 14:04:03 Updating status for
2) In some cases, the transport works nearly as expected (apart from known issues), but the registered ICQ-User is allways treated as Offline/Invisible and not seen by other ICQ-Members.
Any suggestions?
Regards,
Andy