Quote:
Originally Posted by redwildebeast what was delayed??? iniatiating the call or when you were talking??? |
Based on Nokia's description, I think the call itself might have been lagged. When using VOIP, or other Internet Phone technology, there is a minimum bandwidth requirement that is necessary for smooth voice calls. The speed necessary depends on the amount of data that needs to be sent and received, which is directly related to the quality of the call.
I don't know if @Home has a "voice call quality selector" feature (either a button or software control on the router and/or phone), but the lower the quality of call selected, the less data that needs to be transferred to and from T-Mobile's servers real-time. Thus, the lower the quality of calls, the less minimum bandwidth speed necessary to maintain the call. The higher the quality of calls, the more minimum bandwidth speed necessary to maintain the call.
Possible explainations can be that Nokia's DSL speed was too slow (at that time) to effectively use @Home to make stable calls. This can be caused by a bad connection (interference or bottleneck somewhere from the phone to T-Mobile's servers), too slow of a connection (either downlink or uplink) because the DSL modem is too far away from the "box" or the ordered speeds are too slow, too much network activity through the same router/modem at the time of the call without voice prioritizing QOS (like data downloads, video/music streams, online gaming, file transfers, etc), or too much congestion on T-Mobile's servers (like too many callers at once or too few servers at that time).
I've heard quite a few people happy with @Home so far, and only 2 people unsatisfied with the results (Nokia here, and another poster on another forum). Hopefully Nokia (and the other poster) can find out what their problem is and fix them (somehow) so they can enjoy @Home too!
