[JDEV] ICQ Transport with Jabber 1.2 - still getting remote server error

[Dennis Noordsij]

On Tuesday 14 November 2000 13:33, Vincent Lim wrote:

> > Oops, just realised that I actually installed the wrong version of
> libetherx. Searched the cvs and found the version with ehandler_new_ex.
> Compiled it, and re-compiled the icq transport. Compiles well now. But, I
> still cannot get to register the service in JabberIM client. I am still
> getting Remote Server error.
>
> Here's what happens on jabberd when I start the icqtransport:
> =============================================
> Tue Nov 14 19:23:06 2000  base_accept.c:234 Checking:

<snip>

> 7388f559019427ae1ee9ac57789e6fbf49840c1d
> 7388f559019427ae1ee9ac57789e6fbf49840c1d
>
> Here's what happens on icqtransport when I start the icqtransport:
> =============================================
> Tue Nov 14 19:23:06 2000  debug/etherxs.c:91 got node from etherx!
>


Hi

Well, that would actually indicate everything is alright. icqtransport says 
got node from etherx, which means all is good. If there is still an external 
server error, the problem might lie in the configuration files.

Can you write down which ip addresses you use, which dns names they resolve 
to (or in /etc/hosts) as well as provide a copy of your icq_trans.xml and 
jabber.xml files?

For example, if I tell icq_trans.xml that my <etherx><host> is 127.0.0.1, it 
will still connect like in your case, but it will give me server errors 
because I *HAVE* to tell it to connect to icq.mydomain (which in turns 
resolves back to 127.0.0.1, but I STILL have to use the service ID name. ALSO 
in the jabber.xml I must use <service jid="icq.mydomain"> and in the agents 
list the <name> has to ALSO be icq.mydomain. Its quite tricky :) 

You can be happy though that everything compiled fine for you and the only 
thing standing in your way is a configuration error :)

Regards,
Dennis