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

[Keith Minkler]

Vincent,

    try changing the <host> in the icq_trans.xml file to icq.serverIM.com ... also, you may want to concider making the transports appear as sub-domains of the server, (i.e. icq.jabber.serverIM.com -- or making your server serverIM.com, and transport icq.serverIM.com, etc...) but it's not neccessary, and your server will route properly either way.. it's just customary.. =]

-Keith

On Tue, Nov 14, 2000 at 08:04:11PM +0800, Vincent Lim wrote:
> Thanks Dennis,
> 
> I actually tried also with the Yahoo transport,and everything compiled fine, and the 
> yahootrans started up fine too. Then again, when I try to register the service in JabberIM, I get the
> Remote Server error. Yap, I agree, there must be something I am missing or not getting right in the config.
> Hope you can help on this....
> 
> 
> Here's a snapshot of my configuration:
> ===========================
> My server ip is: 192.168.1.2
> All the stuff are installed in the same server.
> I have added jabber.serverIM.com and icq.serverIM.com to my internal DNS.
> 
> 
> In jabber.xml:
> ------------------
> ........
> <host><jabberd:cmdline flag="h">jabber.serverIM.com</jabberd:cmdline></host>
> ........
>         <agent jid="icq.serverIM.com">
>           <name>ICQ Transport</name>
>           <description>This is the ICQ Transport</description>
>           <transport>ICQ#</transport>
>           <service>icq</service>
>           <register/>
>         </agent>
> .........
>   <service id="icq.serverIM.com">
>       <accept>
>          <port>2222</port>
>          <ip>192.168.1.2</ip>
>          <secret>icq-accept</secret>
>       </accept>
>   </service>
> 
> 
> In icq_trans.xml:
> ------------------------
>   <host>
>         <name>icq.serverIM.com</name>
> ....................
>   <etherx>
>     <secret>icq-accept</secret>
>     <host>192.168.1.2</host>
>     <port>2222</port>
>   </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
> 
>