powered by Jive Software

Can''t stay connected to AIM

Both the MSN and Yahoo transports have been working very well for me, but I’‘ve really been struggling to get the AIM transport working since v1.0 and up to v1.0.2. I can’‘t get it to connect. The only thing I’‘ve changed is the oscar port from 5190 to 80 (I’'ve verified that 80 works through our firewall but 5190 is blocked). In the debug log, I get the following when trying to connect…


2007.05.31 16:22:12 Received iq packet: <iq id=“Lo6I2-41” to=“aim.myServer” type=“get” from=“myAccount@myServer/spark”><query xmlns=“http://jabber.org/protocol/disco#info”/></iq>

2007.05.31 16:22:12 aim: Sending packet: <iq type=“result” id=“Lo6I2-41” from=“aim.myServer” to=“myAccount@myServer/spark”><query xmlns=“http://jabber.org/protocol/disco#info”><identity category=“gateway” type=“aim” name=“AIM Transport”/><feature var=“jabber:iq:gateway”/><feature var=“jabber:iq:register”/><feature var=“jabber:iq:version”/><feature var=“jabber:iq:registered”/></query></iq>

2007.05.31 16:22:13 Received presence packet: <presence id=“Lo6I2-42” to=“aim.myServer” from=“myAccount@myServer/spark”/>

2007.05.31 16:22:13 A new session has come online: myAccount@myServer/spark

2007.05.31 16:22:13 Created aim session for myAccount@myServer/spark as ‘‘myAIMid’’

2007.05.31 16:22:13 OSCAR login service state change from NOT_CONNECTED to INITING

2007.05.31 16:22:13 OSCAR login service state change from INITING to RESOLVING

2007.05.31 16:22:13 OSCAR login service state change from RESOLVING to CONNECTING

2007.05.31 16:22:13 OSCAR login service state change from CONNECTING to CONNECTED

2007.05.31 16:22:14 Handling AIM-style auth.

2007.05.31 16:22:14 Got auth response!

2007.05.31 16:22:14 Got something else?

2007.05.31 16:22:14 OSCAR bos service state change from NOT_CONNECTED to INITING

2007.05.31 16:22:14 OSCAR login service state change from CONNECTED to NOT_CONNECTED

2007.05.31 16:22:14 OSCAR bos service state change from INITING to RESOLVING

2007.05.31 16:22:14 OSCAR bos service state change from RESOLVING to CONNECTING

2007.05.31 16:22:14 OSCAR bos service state change from CONNECTING to CONNECTED

2007.05.31 16:22:24 OSCAR bos service state change from CONNECTED to NOT_CONNECTED

2007.05.31 16:22:24 Session myAccount@myServer disconnected from aim.myServer. Reconnecting… (attempt 1)

2007.05.31 16:22:24 OSCAR login service state change from NOT_CONNECTED to INITING

2007.05.31 16:22:24 OSCAR login service state change from INITING to RESOLVING

2007.05.31 16:22:24 OSCAR login service state change from RESOLVING to CONNECTING

2007.05.31 16:22:24 OSCAR login service state change from CONNECTING to CONNECTED

2007.05.31 16:22:24 Handling AIM-style auth.

2007.05.31 16:22:24 Got auth response!

2007.05.31 16:22:24 Got something else?


This repeats until I finally get a “You have connected too many times in too short of a time frame. Please wait around 15 minutes before trying again.” message. Any thoughts?

Thanks!

Kevin

Hrm. I can’‘t vouch for port 80 working at all. I’‘ve never tried it. Where else have you tried port 80? The only time I’‘ve seen port 80 used is with a proxy and there’'s no support for that yet.