Suggestions to T-Mobile for Improvements to @Home ServiceOctober 26, 2008 at 1:16 am | Posted in Uncategorized | Leave a comment
Tags: @Home Enhancements, @Home Service
It’s a valuable feature to truly replace a wireline service. Vonage has it, so it’s feasible over VoIP, although I suspect that it merely may be that UMA does not support FAX, which would explain why T-Mobile can not readily add this feature.
Latest Wi-Fi capabilities (better range)
802.11n support (better range, with compatible devices) as well as the choice of Wi-Fi frequency bands (2.4 or 5 GHz) would be nice, although you can attach your favorite Wireless router to the @Home router and get the benefits of both, but a single device that is current is a better solution.
Some customers desire the ability to manage Call Forward/Call No-Answer settings from a web site, instead of using feature codes that must be entered from the wireline phone. This would undoubtedly make the service more complex and would be of value only to a select audience (not the mainstream). This feature (and others) could be added without complicating the standard setup and use; give the power to those that are ready to use it. Actually, T-Mobile could use this method – a web portal – to add new features (much as Google does with its one number service).
Caller ID Slow
For some customers, they do not receive Caller ID until the 2nd to 3rd Ring (which seems to be related to the issue of fast ring cycles, see below).
Support for Answering Machines
Some @Home customers prefer to use a separate answering machine, and some of those customers have had slight problems with the existing @Home service that could be corrected. Most customers use T-Mobile’s included voice mailbox (and I recommend merging it with your existing mobile phone’s voice mailbox, to avoid having to check two, different voice mailboxes).
Fast Ring cycles => Answering Machine picks up too quickly
Some customers note that their answering machines are cued to record the message too quickly, due to very fast ring cycles from the router.
Caller disconnect not indicated => Answering Machine records busy signal
Suggestion: Drop the line voltage when the calling party disconnects instead of giving a busy signal (so that the answering machine does not record the busy signal). When the caller hangs up after leaving a message, the answering machine can’t detect the hangup and stays connected for 10-15 seconds during the fast busy signal.
“Based on my research on similar problem with other VOIP setups, I suspect the CPC duration (aka Open Loop Disconnect–the amount of time the router has the phone line voltage go to zero to indicate a hang-up) is too short, probably 150-200 ms, and so most answering machines can’t detect it. On other VOIP systems the CPC duration was a setting on the router, but on the 1.004 firmware for this router there are almost no configurable options for the “Voice” settings on the router.”