UMA Settings

[AbsoluteEvel]

I found this on HOFO and figured it should be posted here too... I have configured these settings on two routers that I own (DIR-655 and WRT54GS) and the voice quality seems better...

http://www.howardforums.com/showthread.php?t=1285942

Per Linksys Tech Support, use the following values in your router:

Fragment Threshold : 2304 (256-2346)
RTS Threshold : 2304 (0-2347)
Beacon Interval : 50 (20-1024 ms)

Additionally, RIM tells you to set the DTIM value to 2 here:
"+title+"

[Mystictrust]

Wonderful, thanks for cross-post. Seems like useful information. I'm going to sticky this thread for now.

[analogs]

For what it's worth, I have the official T-Mo Linksys router and these are the default settings, which are pretty similar but not identical to those above:
Fragment Threshold : 2346
RTS Threshold : 2347
Beacon Interval : 100

I've got SBC's 6 megabit DSL (which rocks). Two UMA phones and two to three laptops at any given time, usually bit torrenting or Soulseeking, and I never drop calls.

Also, I thought the T-Mo router used some kind of MAC filtering to prioritize phone packets, similar to QOS on VOIP. The thread on howardsforums hints at it but I don't see anything about it in the firmware and I doubt that the WRT54G series can do that.

[AbsoluteEvel]

I have noticed that UMA seems to work great with the defaults in areas where there is little or no other wifi. I have an average of 6 other networks within range of the two routers I oversee and the problem is that the voice will get jumbled occasionally. When I changed these settings it seemed to do away with the degradation of voice quality.

You just need to give the highest priority level to UDP ports 500 and 4500 to make sure the t-mo voice tunnels have appropriate bandwidth allocated to them. The WRT54G(S/L) series can do port or MAC based QOS. In my case I am running the latest Thibor firmware, but I believe the latest official firmware also includes the functionality.

[clock3687]

I used to use H@H on a linksys WRT54G (v. 7 i think), and it does have QoS filtering either by MAC or by ethernet port. If you want to enable it, log into the router (192.168.1.1) -> Applications & Gaming -> QoS. Enter in the phones MAC address, set the priority to High, and you should be set. The phone calls have always been crystal clear, even while torrenting or gaming. I now own a linksys wrt350n, and setting up qos was very easy. I haven't had any issues with the router since configuring it.

[analogs]

Lately I've been having problems at the same time every day. It seems like there's some kind of network maintenance going on around 9 - 10 PM CST in my area (zip 60647). My phone drops the UMA connection for an hour or two. If I manually try to connect, it says something like "ISP or network error". It's happened for the last three days in a row.

Oh, and thanks for the QOS info. I'll have to check that out when I get home.

[AbsoluteEvel]

Posts on other forums seem to indicate the daily issue we have all been having this past week is in fact a capacity problem. According to T-Mobile's Hotspot@Home support department, this is a known issue and their "#1 priority" issue at the moment.

I was just reading on BGR that T-Mobile has just released their 4th Hotspot@Home phone, so I would expect it will be a while until we see a really reliable UMA service.

Whenever you call to report an issue with UMA, be sure to ask for "Hotspot@Home Support" or "Data Device Hotspot@Home Support" if you have a Curve. They have a dedicated support department just for that, and if those call queues get huge everyday, they will certainly notice that the issue is in fact a big problem and maybe they will fix it quicker.

[rltipva]

my bb curve will not stay in uma for more than a minute at a time. when I first got it I had no problem, but now I DO. I am using a netgear router and I get a great signal in my house. Any suggestions?

[analogs]

Originally Posted by AbsoluteEvel

I would expect it will be a while until we see a really reliable UMA service.

I hate to sound like a whiner but I couldn't agree more. As I mentioned in a previous post, it just doesn't seem like they're taking UMA very seriously. Aside from the mediocre (and I'm being generous) handset selection, you have to wonder what's going on when they release a WiFi capable phone without H@H (the Shadow). The most likely answer is that it was rushed to market. I think someone on here commented that the Shadow development cycle was half of what a typical handset is, which begs the question, why the **** did they have to get it out the door so fast?

Judging by how little discussion there was about it, I have to assume that there weren't more than about fifty people following the UMA story before it launched on T-Mobile. We logically assumed that firmware updates would be released for phones like the MDA to enable UMA. I was convinced, downright sure, that the Wing would get one too, but it didn't. But not having UMA on the Shadow? That's just a kick in the balls. I was so sure that the Shadow would have it that I never even noticed it missing from the Engadget posts. I waited for my paycheck, I was INCHES from buying it, and then BOOM! The news hit me like hearing that your brother just died in a car accident.

Some day...

[Fuzzion]

For myself, and I imagine a lot of others here as well, another big problem can be signal integrity. Meaning... you can have a strong signal, but due to RF noise and other infrastructural/environmental factors, you can have periodic, but momentary drop-outs or fading of the signal. For data, not so much of a problem.... but for voice, that's a big issue

I solved this problem by dropping in a Netgear RangeMax router with MIMO (Multiple Input/Multiple Output). I won't attempt to explain MIMO here, but bottom line, my Wi-Fi voice experience now rivals my land line... no more drop-outs, no fade and excellent voice quality.

Cheers