I have decided to take the router back and use a regular land line for now. I still can’t pinpoint the problem, but I have found that re-flashing the firmware is a temporary fix. For some reason this works, but simply restarting the router doesn’t. So that’s what I have done every other morning for a week: Wake up… no blue light (no phone service)… “upgrade” firmware (for the n-th time)… blue light comes back on (phone works again)… then I just wonder how many calls I missed. This is one of those times when being an early adopter can bite you in the butt. At least I was able to talk T-Mobile into taking it back outside of the 14 day “buyer’s remorse” window. The whole idea that I would have to pay a $200 “early termination fee” is just silly. If a product doesn’t work after a few weeks I should be able to take it back for a refund. Period. 14 days is *barely* enough time to switch your number to T-Mobile and back, so you might want to test out your service with a number you don’t care about first. I know this has worked for others very well, but for some reason the Comcast + T-Mobile combination was a non-starter for me. Anyway, I’ll try VOIP again someday — in a year or so maybe.
Taking T-mobile @home VOIP router back…
- Mac formatting questions I’ve asked myself…
- National Center for Edtech Research Announced
Yeah, I’ve been skeptical about VOIP since the beginning. I have it now (via Comcast) but still have minor issues every once in a while. Say what you want about the old school POTS phone lines, but it just always worked.
At least you got a blue light at all. I’m still trying to get it work with my Verizon DSL, but no luck after 3 weeks. I’m giving up Tuesday.