My bad…
Ok, So it would seem that a great many people are interested in my post on how-to get AIM Phoneline working with iChat.
I had personal business to attend to so I had let my site go stale. After the drive crash, I just took the site down due to lack of personal time. ….. but things are back up now! So here is an update.
What you need to know
This only allows for incoming calls. When I originally configured everything for iChat it worked. I did start to notice that every 4th or 5th incoming call would either be dropped, or sent right to VM. Initially everything worked as promised by AIM, yet over time things started to break or have additional problems.
Problemo Problemo
The first problem that started was the notification to my phone. I set an email forwarder to send a txt message to me if someone called. That way I can be notified if I am out and get a VM so that I can check it. Turns out that worked only 25% of the time and now I do not even get txt messages or emails from it anymore.
(I use AIM mobile forwarding to forward my AIM to my iPhone as soon as I am not signed online. I have been using it for years. This automatically routes the AIM message to my phone as a txt and then I can reply with a txt that will be routed to the AIM user on the other end. I have noticed over this period of time I will have to go in and reset my settings, and reinitialize my phone every once in a while because the messages stop sending properly and end up in /dev/null. I have no idea how AOL’s network is set up, but do the two services share infrastructure? Possibly, Probably.)
Calls garbled, delayed, echoing, or just not initiating was my next problem. When I stopped getting messages and it was garbling or just not even initiating calls, I just plain stopped giving out the number.
Also, of note… I was/am using Chax iChat Component.
For your reference, I was using it on an Intel Macbook Pro on version lower then Tiger 10.4.10 and version lower then iChat 3.1.8 with Chax iChat Component installed.
So, what is the deal with it now?
Software updates or network routing changes broke it or do break it. Who knows if it works on PPC or not? NAT routing might break it. Lack of UPNP support in your router might break it. OSX firewall could break it. Since it is an unsupported feature they have no reason to try and not break it. *It is unsupported since it is potentially buggy, or just plain busted for lots of people, which is why it is only officially supported on AIM Windows.*
Again, sorry I did not update everyone months earlier. Check back though for other goodies, I am going to try and come up with a neat hack per week at least, some with video how-to’s.
Stay Frenchy :{)
*I mentioned this in the last post…
Mr. French @ 12:49 pm
These icons link to social bookmarking sites where readers can share and discover new web pages.