Tags: uma
$19/month "Unlimited" cellular?
There were a few teasers, but it looks like Republic Wireless is launching today (11/8/2011) with its fairly revolutionary cellular plan.
You get:
- Mostly unlimited talk, text, and data for $19 a month.
- No contract.
- $199 initial cost which ships you a LG Optimus S Android smartphone.
The Optimus S you get has been modified to seamlessly use WiFi whenever it is connected, switching to Sprint's cellular network as a fallback when you are not. What's the catch? You have to conform to a certain, but common, user profile where you are connected to WiFi most of the time. Apparently the cut off point where Republic starts sending you concerned correspondence is some combination of 550 minutes, 150 texts, and 300 megabytes of data used on the cellular network. Anything you use while on WiFi anywhere in the world *is*, however, truly unlimited.
If you're around WiFi more than cellular networks, like Alice and I, this might just be a great deal.
Fixing unreliable WiFi UMA connections
Alice and I have the remarkably bad luck of always living in a place where there is no cellular reception. As a result, our phone options are limited to getting a land line (not going to happen) or using T-Mobile's WiFi calling. Since we almost always have access to WiFi at home and at work, it's really a great solution to cellular reception woes. We're firmly in the fixed-mobile convergence camp.
The downside of UMA over WiFi is that it isn't always rock solid, with the chance of annoying latency and dropped calls. If you google UMA problems you will find a bunch of "solutions" ranging from opening ports on your router, enabling IPSec, changing router channels, and putting aluminum foil on your head. In our current living situation, we don't have access to the router, so our options were a bit limited. Both my Blackberry 8120 and Alice's Blackberry 8320 were dropping out of UMA constantly and we were on the verge of buying a Verizon prepaid phone to get us through this. Note: Verizon prepaid plans really suck, so you can see the level of desperation.
Finally I ran into a forum post somewhere suggesting reconfiguring the phone's WiFi connection to static IP address from the default of dynamic. Well, it worked! Both phones are rock solid on UMA now saving months of frustration for just a few minutes of work.
- Options > WiFi Connections > Edit (ConnectionName) > uncheck "Automatically obtain IP address and DNS".
- Enter in a valid IP, subnet, DNS and Gateway.
- Save, exit, and restart the WiFi on the phone.
Good luck, and long live UMA.
For a list of phones that support UMA or WiFi calling, Smart-wi-fi.com is a reliable and complete reference.
Update: In my excitement over UMA working all day, I may have posted this a little prematurely. Alice's UMA dropped the next day. It seems to be an improvement, but it isn't a final solution. The UMA error code is W006.3 - ISP or T-Mobile network error.
Meaning: The phone is unable to establish network connectivity: This could be a problem on the ISP side or the network side.
1. The connection to the WAN port of the wireless router is down: either the cable is unplugged or the DSL/Cable modem (whichever applies) is turned off. This could also be caused by an outage of the DSL/Cable service.
2. Check if MAC filtering is enabled on the wireless router. If it is, check that the phone MAC address is on the Safe List, if not, add it.
3. The network that the user is trying to connect to uses Web Redirection: this means that when trying to connect to the network in question with a laptop, you are required to enter username and password or pay to use the service. The phone cannot connect to such networks.
4. IPSec is not enabled on the router you are trying to use. Enable it in the router settings and try again.
5. The problem can be caused by network issues. At this point, the user might want to try at a later time.
I can rule out 1, 3, and 5 since my phone was still connected. There is no reason for MAC filtering to be enabled, leaving only #4 as a likely option. I am going to take a wild guess and say that we still need IPSec enabled on the router.

11/08/11 09:17:37 am, 