Creating DIY mobile reception with Google Voice and VOIP

Like many people in the USA who live in rural communities, I have no cellular reception at home. My mobile provider, T-Mobile, does not have enough economic incentive to build a tower close to my home. Also, they have not yet seen fit to give me the privilege of paying to compensate for their lack of service via a Femtocell.

Fortunately I have found a solution: Google Voice + Gizmo5 + Sipdroid. Google Voice is a free service which lets it’s users unify all their phones under one number. Simply give friends, family and coworkers that one number, and calls will ring through to whatever phones the user chooses, based upon rules they define. Gizmo5 is a SIP provider that can connect to Google Voice and allow users to make phone calls over the Internet. Gizmo5 has been bought by Google, so registration is currently closed. However, everyone expects that it will eventually be integrated with Google Voice. Finally, Sipdroid is a nice, Open Source SIP client for Android that can connect to services like Gizmo5.

I’ve played with this combination before, when I was using a G1 Android phone from HTC. The reasons I did not stick with it then were because the G1′s battery life was pretty bad, and the G1 struggled enough with performance that it was not feasible to keep Sipdroid running in the background.

Now that I have the amazing Nexus One though, all this has changed. The battery life on the N1 is pretty good by smart phone standards, and it’s performance is high enough that I can easily run Sipdroid in the background all the time without any noticeable performance impact.

I’m using my home WiFi for Sipdroid. I have always been told that WiFi eats battery life rather quickly. However, I’ve been surprised at how much this has not been the case. After a full day of being connected to wireless almost all the time, WiFi only used up about 2% of my phone’s battery (this is with moderate use of the connection). I’ve come to the conclusion that simply having wireless connected does not use much power, but actually transferring data does.

This solution has been working great, but has not been completely without problems. When I receive calls, both parties (the person I talk with and I) have excellent sound quality. However, when I initiate the call via my phone, the person on the receiving end gets tons of latency and a lot of static. I have worked around this issue by initiating the calls via the Google Voice web interface. This hack is slightly annoying, but it is not too bad since I almost always have my laptop on.

After a few days of use, I am quite happy with this solution, and am looking forward to hopefully seeing VOIP kill off traditional telephone providers in the future. AT&T, T-Mobile and others should be very afraid, especially if municipal WiFi becomes more common.

Tags: , , , , , ,

Comments are closed.


AWSOM Powered