[JDEV] ICQ Transport with Jabber 1.2

[Eric Bowersox]

Since I myself have not yet gotten the ICQ transport to work with the 1.2
server, I can't really answer that question yet.
 
The old ICQ transport cannot connect to a 1.2 server.  I have put code in
the new ICQ transport that will allow it to connect to the 1.2 server under
the right conditions, but we have been unable thusfar to get it to work.
(This, incidentally, is one of the major stumbling blocks that keeps me from
releasing the new transport at this time.)
 
                    Eric

-----Original Message-----
From: Vincent Lim's Yahoo [mailto:happiedwf at yahoo.com]
Sent: Sunday, November 12, 2000 11:22 PM
To: dennis.noordsij at wiral.com; jdev at jabber.org
Subject: [JDEV] ICQ Transport with Jabber 1.2


Hi,
 
I noticed your posting about getting the ICQ transport to work with Jabber
1.2. 
I tried too, and was able to get the ICQ Transport to compile.
 
After starting up the jabberd daemon, I started up the ICQ transport.
Everything went smoothly.
I noticed that the jabberd daemon acknowledge that the ICQ transport coming
online because the 
debug mode showed something like '...legacy server incoming connection
established from .....'.
 
On connecting a JabberIM client to my jabber server, I tried to register the
ICQ service, but I get an error.
The error shows .....502: Remote Server Error.
 
Is there something I need to do? 
And, since there is no more separate etherx component in Jabber 1.2, where
do you specify 
the 'secret' key, which is present in icq_transport.xml?
 
 
Regards
Vincent