* Jamin W. Collins ([EMAIL PROTECTED]) wrote: > > Are you manually sending the XML? Have you tried using a Jabber client > to register with the server? Did you set the host name of the server? > Yes, no, and yes. I was using telnet to test jabber itself. Rather tedious, but a bit of an introduction to XML format, so I guess it's not all bad. :-)
<snip> > > I've never used gaim, all testing has been done using Psi as the Jabber > client. I do have the AIM transport installed and working here using > the instructions in the package. > Further attempts to use gaim revealed the existence of a jabber option, but it wants to register me with jabber.org. That's fine, but it sort of defeats the purpose. Now the thing crashes. Psi I don't know, but will try next. > Provided the aim transport is running on the same host as the Jabber > server, yes. The jabber-aim package is configured to create a seperate > instance of jabber that runs only the AIM transport. This seperate > instance then connects to your main Jabber process and provides the AIM > functionality. So, the main jabber.xml has to be configured to listen > for and accept connection from an external process. The instructions > for this are provided in the jabber-aim package's documentation. And I have tried to follow them, though I expect I've missed something. > If you'd like, I could take a look at your configuration file (just > e-mail it to me privately). > That would be most kind, and I shall do that. Thank you once again Cam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
