powered by Jive Software

PyAIMt: unable to communicate with AIM users

I have setup the PyAIMt gateway, but I am uncertain if I have done it properly. The Wildfire web interface shows it under componant sessions, with the AIM logo and the log files in PyAIMt and Wildfire seem to indicate that everything is working properly, but I am unable to message or see anyone who is logged onto AIM. I also tried logging into my normal AIM account without any success.

Here is the debug log from wildfire:

2006.03.05 18:51:47 Connect Socket[addr=/127.0.0.1,port=45820,localport=5347]

2006.03.05 18:51:47 Starting registration of new external component for domain: aim.jabber.myserver.com

2006.03.05 18:51:47 Send stream header with ID: 56917ed8 for component with domain: aim.jabber.myserver.com

2006.03.05 18:51:47 External component was registered SUCCESSFULLY with domain: aim.jabber.myserver.com

Here is the output of the PyAIMt logs:

Debug logging enabled.

Config: Created configuration entity

Setting config option jid = aim.jabber.myserver.com

Setting config option confjid = chatrooms.aim.jabber.myserver.com

Setting config option spooldir = …/pyaim-t

Setting config option pid = PyAIMt.pid

Setting config option mainServer = 127.0.0.1

Setting config option mainServerJID = jabber.myserver.com

Setting config option website = http://jabber.myserver.com/

Setting config option port = 5347

Setting config option secret = mypassword

Setting config option lang = en

Setting config option aimServer = login.oscar.aol.com

Setting config option aimPort = 5190

Adding myserver@myserver.com to config list admins

Using XDB driver xmlfiles

PyTransport: Service starting up

ServerDiscovery: Created server discovery manager

ServerDiscovery: Adding feature support “http://jabber.org/protocol/disco” “None” “aim.jabber.myserver.com

ServerDiscovery: Adding feature support “http://jabber.org/protocol/disco” “None” “chatrooms.aim.jabber.myserver.com

ServerDiscovery: Adding feature support “http://jabber.org/protocol/disco” “None” “USER”

ServerDiscovery: Adding identity “gateway” “aim” “AIM Transport” “aim.jabber.myserver.com

ServerDiscovery: Adding feature support “http://jabber.org/protocol/xhtml-im” “None” “USER”

ServerDiscovery: Adding identity “gateway” “aim” “AIM Transport Chatrooms” “chatrooms.aim.jabber.myserver.com

ServerDiscovery: Adding identity “conference” “text” “AIM Transport Chatrooms” “chatrooms.aim.jabber.myserver.com

ServerDiscovery: Adding feature support “jabber:x:conference” “None” “chatrooms.aim.jabber.myserver.com

ServerDiscovery: Adding feature support “jabber:iq:conference” “None” “chatrooms.aim.jabber.myserver.com

ServerDiscovery: Adding feature support “jabber:iq:register” “” “aim.jabber.myserver.com

RegisterManager: Created

ServerDiscovery: Adding feature support “http://jabber.org/protocol/commands” “” “aim.jabber.myserver.com

ServerDiscovery: Adding node item “http://jabber.org/protocol/commands” “” “command_CommandList” “aim.jabber.myserver.com” “True”

ServerDiscovery: Adding feature support “jabber:iq:gateway” “” “aim.jabber.myserver.com

ServerDiscovery: Adding feature support “jabber:iq:version” “” “aim.jabber.myserver.com

ServerDiscovery: Adding feature support “jabber:iq:version” “” “USER”

ServerDiscovery: Adding feature support “vcard-temp” “” “USER”

ServerDiscovery: Adding feature support “vcard-temp” “” “aim.jabber.myserver.com

ServerDiscovery: Adding node item “updatemyvcard” “” “command_UpdateMyVCard” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding feature support “jabber:iq:search” “” “aim.jabber.myserver.com

ServerDiscovery: Adding feature support “jabber:iq:avatar” “” “USER”

ServerDiscovery: Adding feature support “storage:client:avatar” “” “USER”

ServerDiscovery: Adding node item “stats” “” “command_Statistics” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “connectusers” “” “command_ConnectUsers” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “changepassword” “” “command_ChangePassword” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “changeemail” “” “command_ChangeEmail” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “formatscreenname” “” “command_FormatScreenName” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “emaillookup” “” “command_EmailLookup” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “confirmaccount” “” “command_ConfirmAccount” “aim.jabber.myserver.com” “False”

ServerDiscovery: Adding node item “aimuritranslate” “” “command_AIMURITranslate” “aim.jabber.myserver.com” “False”

PyTransport: Connected to main Jabberd server

ServerDiscovery: onIq element “”

ServerDiscovery: Iq received “component.jabber.myserver.com” “60-4”. Looking for handler

ServerDiscovery: Replying to disco#info request from “component.jabber.myserver.com” “60-4”

Found identity gateway aim AIM Transport

Found feature http://jabber.org/protocol/disco

Found feature jabber:iq:register

Found feature http://jabber.org/protocol/commands

Found feature jabber:iq:gateway

Found feature jabber:iq:version

Found feature vcard-temp

Found feature jabber:iq:search

Here is my config.xml file:

<!8088>

<!mypassword>

<!epoll>

<!kqueue>

<!poll>

<!xmlfiles>

<!mysql>

<!<xdbDriver_mysql>>

<!pyaimt>

<!pyaimt>

<!pyaimt>

<!localhost>

<!</xdbDriver_mysql>>

<!xmlfiles>

<!<xdbDriver_xmlfiles>>

<!encrypted>

<!</xdbDriver_xmlfiles>>

I don’'t know what I am doing wrong, please help.

I did find this after attempting to add a contact in spark.

2006.03.05 22:42:47 Closing session due to incorrect hostname in stream header. Connection: org.jivesoftware.wildfire.net.SocketConnection@31db04 socket: Socket[addr=/192.168.1.81,port=44100,localport=5269] session: null

What does this mean?

What client? Have you registered with AIM Gateway? You have to register with it and enter your AIM account login&pass.

My apologies. I was finally able to get it working.

Two things were wrong. The first is that I was unfamiliar with registering the AIM account and password. This needed to be done using something other than Spark (I used Pandion). Once Pandion was able to register the transport I was able to switch back to Spark, which accepts AIM users being added to the contact list now. Its amazing how many times I saw in other posts that it was necassary to do this and I dismissed it thinking I had a different problem.

The second thing was Gentoo had a seperate install for xish.domish (actually called ‘‘twisted-xish’’). Once that was installed a few warnings were displayed when running PyAIMt, but the AIM transport works. I would not have found this if it wasn’'t for the errors I origionally received from attempting to connect to the transport with Pandion. This led me to experiment and update Python and Twisted. Once I had done that, I started receiving errors from PyAIMt about the xish.domish. To resolve this I installed twisted-xish (emerge twisted-xish).

Thank you for your help!

Message was edited by: ooky