[hd_rider]

I have a Curve 8320 with WiFi. On my home network, my device connects via WiFi without any problem and goes to UMA mode readily. My home wireless router is set to use 802.11g and WEP.

My wireless network at work uses Cisco hardware and LEAP protocol. My device connects to this network via WiFi as well. However, I cannot get UMA and the device remains on the EDGE network.

My network signal strength at home is typically above 90% while my wireless network strength at work averages around 50%.

So I'm wondering, is UMA directly dependent on the strength of the wireless signal or does it require a specific protocol or specific method of encryption?

Sorry, but I'm not a 'network' person and am just trying to understand the functionality of my device a little better. Thanks in advance.

[6502programmer]

Does the WiFi indicator light up for you, or does it stay grayed out? It might be helpful to include the wifi diagnostics output. Feel free to redact SSID's and MAC addresses.

[hd_rider]

Yes, the WiFi indicator is lit up and I am able to browse the internet via the WiFi browser. WiFi diagnostics indicate that I am able to connect to my WAP at work using 802.11a/g and LEAP security, signal level -77 dBm. UMA diagnostics indicate that UMA Wi-Fi is available (green check mark) but that the connection fails due to a W006.1 error. I'm wondering if the firewall on my company's network is causing the authentication error.

[6502programmer]

That is quite possible. IIRC, TMO UMA goes over UDP ports, and the BB Data goes over a standard SSL (TCP) connection. It is quite possible they've blocked outbound UDP.

[John Clark]

-77db is getting a little low. It's possible that is the problem. Can you get closer to the router?

[pulrang]

I have the same exact issue. I am connected (bright wi-fi icon) with UMA at home. However at work, I am connected (same bright wi-fi icon) with EDGE. Very frustrating trying to figure out why. I was wondering if it may be due to poor signal strength so I put the phone right on the router with no UMA still.
Now I am wondering if there is not enough bandwidth to support the UMA connection but T-Mo states it only uses 50-80k. I will post back if I find anything.

[John Clark]

If it works other places except there, then it's obviously an issue with the router/isp. Some places work good, others don't.

[pulrang]

That would be why I am posting here - to see if others have had this issue too and what they did to resolve it. However, in the meantime, I will continue to troubleshoot the router/firewall/ISP between the BB and T-Mo.

[pulrang]

For full disclosure on my current setup:
BlackBerry connects dynamically to DLink Dl-824VUP and gets a 192.168.1.x address. DLink connects to my company's internal network and has a fixed IP of 192.168.0.29 on my company's 192.168.0.x subnet. My company's internal network is connected to internet via a hardware firewall which is connected to a T1. My firewall allows all traffic outbound over ports 80, 443, 3389 etc. UMA uses port 443.

I found that when my 8320 connects to the DLink and tried to initiate the UMA connection, 192.168.0.29 was making requests to what I assume to be a T-Mobile IP address over random ports. Hence they were being blocked. I then allowed 192.168.0.29 full access to the internet and UMA came alive. The line from my log that showed a successful connection for UMA is below:
Source - 192.168.0.29:57277
Destination - 216.9.242.88:443
Access Allowed

This was blocked before I opened up the firewall.

I am guessing that others may have a simple access point that gives an address on the main subnet (if that were the case in my example the 8320 would have a 192.168.0.x address). If you are in this situation and you need to open a hole in the firewall, remember you can fix the IP address in your BlackBerry by unchecking the box next to 'Automatically obtain IP address and DNS' in Wi-Fi Options>[Saved Profile Name]>Edit dialog.

I hope this will help someone figure out their issue down the road.