T-Mobile @Home Service Problems

My friend, Brett, and I both traded in our Vonage service for T-Mobile’s new @Home VoIP solution. How could we not?

Vonage was running about $30/month for their unlimited domestic plan (fees and taxes included), whereas T-Mobile advertised basically the same service for $10/month (so long as you also have a $39.99+ mobile plan). Add that all up and it’s $240/year.

The T-Mobile ATA (analog telephone adaptor) is a Linksys WRTU54G-TM with combines a router, firewall, wireless B/G Wi-Fi access point, and 4-port switch with the ATA functions (two phone lines with two SIM slots). This meant that I could get rid of my Netgear router/firewall/WAP/switch and the Vonage ATA. Less equipment usually means less heat, fewer potential points of failure, and typically uses less power (note, I haven’t actually measured heat output nor power consumption of the two solutions, I’m only making generalizations).

I had some fairly substantial complications getting setup initially but once the LNP (local number porting)was (fully) complete I thought I’d be all set with Vonage-esque reliability.

Recently we’ve notices a rather peculiar trend: we’ll go to make a phone call and won’t have a dial-tone. A check on the ATA shows all lights blinking away happily, internet traffic is still buzzing away, wireless traffic is still getting through. For all intents and purposes, the ATA is doing everything except being an ATA. After I unplug the ATA (wait 15 seconds) and plug it back in, I have a dial-tone within 90 seconds. Apparently something is happening to interrupt the registration between the ATA and T-Mobile’s servers. I don’t know if this is an issue with the ATA (I’d assume not, since all other functions are working), the Internet/ISP (I’d assume not, since all other internet traffic is flowing), or something on T-Mobile’s end.

In any event, I shared my experience with my buddy, Brett. He says he’s experiencing the same thing about once a month. My experience is a bit more frequent than that.

Anyone else having this type of problem with T-Mobile’s @Home service?

← All articles