Uma Just Won't Work!

**curlin31** · 03-12-2009, 04:35 AM

My UMA has not connected since mid January on either the 8320 or the 8900. I've had countless trouble tickets opened with T-Mobile and nothing has been resolved. I've tried everything on my end, and the UMA just won't connect. Doesn't matter what wifi network, what type of router, or ISP. Sim Card has been swapped twice. Wifi Profiles in question have been deleted and re-saved. I'm at a complete lost as to why this won't work.
Here is an advanced WIFI Diagnostic Report:

Wi-Fi
Current Profile: CurlinNet
SSID: CurlinNet
AP MAC Address: 00:0F:B5:66:30:66
Security Type: WEP
Association: Successful
Authentication: Successful
Local IP Address: 192.168.1.5
Signal Level: -48 dBm
Connection Data Rate: 48 Mbps
Status: Network acquired
Authentication Failure Reason:
Network Type: 802.11b/g
Network Channel: 11
Pairwise Cipher: Not Applicable
Group Cipher: Not Applicable
Gateway Address: 192.168.1.1
DHCP: Successful
Primary DNS: 192.168.1.1
Secondary DNS: 0.0.0.0
DNS suffix:
Subnet Mask: 255.255.255.0
Server Domain Suffix:
Certificate: Not Applicable
Software Token: Not Applicable
L3 Auth:

VPN
Current Profile:
Concentrator Address:
Contact: N/A
Authentication: N/A
Secure Device IP:
Status: VPN disabled.
Resolving Concentrator: N/A
Concentrator IP:
Primary DNS:
Secondary DNS:
DNS Suffix:
Secure Subnet Mask:
Retry at:
Session Lifetime:
Re-login at:
Failed Login Attempts:
Certificate:
Software Token:

UMA
Connection Pref.: Wi-Fi Preferred
UMA Wi-Fi Available: Successful
Connection: Error
Error Code: W006.1
Status: ISP or T-Mobile Network error.
Reg. UNC Address:
Registration: Error
Authentication: Error
Serving UNC Address: punc.t-mobileuncs.com:14001
Security Gateway Address: psgw.t-mobilesgws.com
Cell Info.:
Cell. handover to UMA failures: 0
Cell. rove-in failures: 0

BlackBerry Infrastructure
Address Used: //rcp.na.blackberry.com:443
IP Used: 204.187.87.88:443;60332
Connecting: Successful
Authenticating router: Successful
Authenticating server: Successful
Last Contact At: Mar 12, 2009 4:26 AM

Sent wireless via my T-Mobile Blackberry Curve

This is exactly what i've seen since January in every wifi network. Any Ideas???

Thanks

**dvaskelis** · 03-12-2009, 10:12 AM

I routinely got similar errors with my Linksys WRT600N. I ended up turning off the 600N's 2.4GHz radio and plugging in an old WRT54GS (running Tomato) and have had zero UMA issues since.

**ndnoutlaw** · 03-12-2009, 02:53 PM

I tried running without wep....no password and it worked.
also I can use the wifi from other unsecured devices in the area.
if anything, I call 611....ask directly for customer service, then ask for blackberry techs....go through their battery pull mumbo jumbo, then they will get to the meat of your issue. they might be able to drop an upgraded system to you at the same time.
good luck

**curlin31** · 03-12-2009, 03:56 PM

I wish it were router or network or even ISP specific but it's not.... it's not even device specific lol. The only common denominators are me, and T-Mobile lol.

**blackops** · 03-12-2009, 10:15 PM

Same messages I got when I was with T-mo. Never did get UMA to work.

**ApproachShot** · 03-14-2009, 04:14 PM

Curlin31, ... don't know what router you are using, but I had similar UMA problems I thought were the fault of a new BB 8320 and then a new BB 8900 that went away when I updated the driver for the wireless card in my laptop! I updated the firmware version for the T-Mo wireless router (Linksys WRT54G-TM) at the same time, but I think that had little or nothing to do with the problem disappearing. If you are using the same wireless router for your BB that you are using to link wireless PCs in your home network, give this a try. Feel free to PM me if you want or need instructions how to update the driver for the wireless card in your PC/laptop and/or how to update the firmware for your router. It took many calls to T-Mo support people before I got a pretty savvy tier 3 router support guy who came up with this fix for me.

**curlin31** · 03-18-2009, 07:02 PM

Thanks for the reply, but the issue isn't network or router specific. It hasn't worked in countless wifi networks with countless different routers and countless different ISPs.

**sonoro** · 03-19-2009, 01:04 AM

Have you tried removing the battery?

**truoc444** · 03-19-2009, 07:40 AM

Mine had major problems until i changed the broadcasting of my router from B/G/N to G only. Seems to have helped. The newest software update helped too. Good thing I have more than one router. I use one for my phone g only and a different one for my laptop running N.

**ApproachShot** · 03-19-2009, 05:32 PM

With respect, curlin31, when I've been as frustrated as it sounds like you are, the solution to seemingly unsolvable problems like this one you are having have almost always turned out to be some small thing I had either overlooked or already dismissed as impossible. The driver for my laptop that was the actual source of my 8320's and 8900's UMA problems is an example. The incongruous B/G/N frequency signals that truocc444 mentioned was the source of his/her problem is another. See if you can give up the notion that you've tried everything in "countless" configurations, and nothing is going to work. If you'll PIN me a message, I'll share the name, number and work shift hours of the Tier 3 Unlimited Hot Spot Support guy at T-Mo who solved the riddle for me that no one else there or elsewhere was able to solve. T-Mo has 7 such similar support groups around the country, so it is not likely that you will be fortunate enough to reach this guy on your first call, but he has returned calls when I've specifically asked for him by name in the past. Start fresh with this guy and let him have a go at helping you get to the bottom of the problem. Good luck.

**curlin31** · 03-24-2009, 11:12 PM

So, my UMA randomly started working again. And the problem is just what I thought it was, the Serving UNC and Gateway address issued by T-Mobile. Check out my diagnostic report before and after and notice the difference:

BEFORE

Wi-Fi
Current Profile: CurlinNet
SSID: CurlinNet
AP MAC Address: 00:0F:B5:66:30:66
Security Type: WEP
Association: Successful
Authentication: Successful
Local IP Address: 192.168.1.5
Signal Level: -48 dBm
Connection Data Rate: 48 Mbps
Status: Network acquired
Authentication Failure Reason:
Network Type: 802.11b/g
Network Channel: 11
Pairwise Cipher: Not Applicable
Group Cipher: Not Applicable
Gateway Address: 192.168.1.1
DHCP: Successful
Primary DNS: 192.168.1.1
Secondary DNS: 0.0.0.0
DNS suffix:
Subnet Mask: 255.255.255.0
Server Domain Suffix:
Certificate: Not Applicable
Software Token: Not Applicable
L3 Auth:

VPN
Current Profile:
Concentrator Address:
Contact: N/A
Authentication: N/A
Secure Device IP:
Status: VPN disabled.
Resolving Concentrator: N/A
Concentrator IP:
Primary DNS:
Secondary DNS:
DNS Suffix:
Secure Subnet Mask:
Retry at:
Session Lifetime:
Re-login at:
Failed Login Attempts:
Certificate:
Software Token:

UMA
Connection Pref.: Wi-Fi Preferred
UMA Wi-Fi Available: Successful
Connection: Error
Error Code: W006.1
Status: ISP or T-Mobile Network error.
Reg. UNC Address:
Registration: Error
Authentication: Error
Serving UNC Address: punc.t-mobileuncs.com:14001
Security Gateway Address: psgw.t-mobilesgws.com
Cell Info.:
Cell. handover to UMA failures: 0
Cell. rove-in failures: 0

BlackBerry Infrastructure
Address Used: //rcp.na.blackberry.com:443
IP Used: 204.187.87.88:443;60332
Connecting: Successful
Authenticating router: Successful
Authenticating server: Successful
Last Contact At: Mar 12, 2009 4:26 AM

AFTER

Wi-Fi
Current Profile: CurlinNet
SSID: CurlinNet
AP MAC Address: 00:0F:B5:66:30:66
Security Type: WEP
Association: Successful
Authentication: Successful
Local IP Address: 192.168.1.6
Signal Level: -48 dBm
Connection Data Rate: 48 Mbps
Status: Network acquired
Authentication Failure Reason:
Network Type: 802.11b/g
Network Channel: 11
Pairwise Cipher: Not Applicable
Group Cipher: Not Applicable
Gateway Address: 192.168.1.1
DHCP: Successful
Primary DNS: 192.168.1.1
Secondary DNS: 0.0.0.0
DNS suffix:
Subnet Mask: 255.255.255.0
Server Domain Suffix:
Certificate: Not Applicable
Software Token: Not Applicable
L3 Auth:

VPN
Current Profile:
Concentrator Address:
Contact: N/A
Authentication: N/A
Secure Device IP:
Status: VPN profile is not found.
Resolving Concentrator: N/A
Concentrator IP:
Primary DNS:
Secondary DNS:
DNS Suffix:
Secure Subnet Mask:
Retry at:
Session Lifetime:
Re-login at:
Failed Login Attempts: 0
Certificate:
Software Token:

UMA
Connection Pref.: Wi-Fi Preferred
UMA Wi-Fi Available: Successful
Connection: Successful
Error Code:
Status: UMA Connection successful.
Reg. UNC Address:
Registration: Successful
Authentication: Successful
Serving UNC Address: n43.w89.t-mobileuncs.com:14001
Security Gateway Address: n43.w89.t-mobilesgws.com
Cell Info.: MCC:310 MNC:26f Cell ID:65504 ARFCN:810
Cell. handover to UMA failures: 0
Cell. rove-in failures: 0

BlackBerry Infrastructure
Address Used: //216.9.242.88:443
IP Used: 216.9.242.88:443;52464
Connecting: Successful
Authenticating router: Successful
Authenticating server: Successful
Last Contact At: Mar 24, 2009 11:03 PM

Sent wireless via my T-Mobile Blackberry Curve

I called T-Mobile and let them know that the issue had been resolved (and that their tech support failed miserably) and initially they tried to offer a measly $10 credit with the justification that my problem didn't cause me to incur any overages or fees (nevermind that it was a complete inconvenience). So I talked to a supervisor and stressed the value the 8320 and 8900's UMA capabilities to me, and how often I used it, and she got me a $60 credit. Kind of wanted more, but I settled. I'm just happy to see my precious pink bars again

Thanks to everyone for their support and advice!

**I8UB4** · 03-25-2009, 12:30 AM

How did you change the Serving UNC and Gateway address issued by T-Mobile?

**tw1tch01** · 03-25-2009, 12:40 AM

Yes I'd love to know how you made those changes to your UMA settings!!?

**curlin31** · 03-25-2009, 01:22 AM

There isn't a way.... it's at complete random. The best you can do is talk to tech support and hope you get someone that knows what the **** you're talking about (I never did) or try offering to email a tier 3 tech that advanced diagnostic and see what they think

**I8UB4** · 03-25-2009, 12:37 PM

Originally Posted by curlin31

There isn't a way.... it's at complete random. The best you can do is talk to tech support and hope you get someone that knows what the **** you're talking about (I never did) or try offering to email a tier 3 tech that advanced diagnostic and see what they think

so you didn't do anything and one day it just started working?

**curlin31** · 03-25-2009, 12:39 PM

Advanced tech support actually just called me to verify that the problem was fixed. They said that the engineers completely removed my device from the failed UNC and Gateway addresses and assigned a new one which explains why it started working. I thought that they had forgotten about me lol....once again T-Mobile's customer care impresses me.

Posted from my CrackBerry at wapforums.crackberry.com

**sj3ff** · 03-26-2009, 03:02 PM

Wouldn't happen to have an email address for your adv tech support rep would you?

Trying to avoid the looong haul call to tech support...

I spent an hour in a chat seesion with a rep yesterday only to find out she could not log a ticket about the issue. I have to call in to create a ticket.

The issues you were describing are the same thing I am seeing. It is so random that it is pathetic.

Here is my Wifi Diag.

Wi-Fi
Current Profile: *Edited*
SSID: *Edited*
AP MAC Address: 00:1C:10:AE:6F:EE
Security Type: Pre-Shared Key (PSK)
Association: Successful
Authentication: Successful
Local IP Address: 192.168.1.102
Signal Level: -27 dBm
Connection Data Rate: 48 Mbps
Status: Network acquired
Authentication Failure Reason:
Network Type: 802.11b/g
Network Channel: 9
Pairwise Cipher: TKIP
Group Cipher: TKIP
Gateway Address: 192.168.1.1
DHCP: Successful
Primary DNS: 216.136.95.2
Secondary DNS: 64.132.94.250
DNS suffix:
Subnet Mask: 255.255.255.0
Server Domain Suffix:
Certificate: Not Applicable
Software Token: Not Applicable
L3 Auth:

VPN
Current Profile:
Concentrator Address:
Contact: N/A
Authentication: N/A
Secure Device IP:
Status: VPN disabled.
Resolving Concentrator: N/A
Concentrator IP:
Primary DNS:
Secondary DNS:
DNS Suffix:
Secure Subnet Mask:
Retry at:
Session Lifetime:
Re-login at:
Failed Login Attempts:
Certificate:
Software Token:

UMA
Connection Pref.: Wi-Fi Preferred
UMA Wi-Fi Available: Successful
Connection: Error
Error Code: W006.1
Status: ISP or T-Mobile Network error.
Reg. UNC Address:
Registration: Error
Authentication: Error
Serving UNC Address: punc.t-mobileuncs.com:14001
Security Gateway Address: psgw.t-mobilesgws.com
Cell Info.:
Cell. handover to UMA failures: 0
Cell. rove-in failures: 0

BlackBerry Infrastructure
Address Used: //216.9.242.88:443
IP Used: 216.9.242.88:443;55872
Connecting: Successful
Authenticating router: Successful
Authenticating server: Successful
Last Contact At: Mar 26, 2009 2:57 PM
Sent via BlackBerry from T-Mobile

**curlin31** · 03-26-2009, 07:59 PM

No I don't have an email, but yea, that's the exact same problem. Just stick it out and file the ticket. Apparently the found and fixed the problem for me and it's been working consistently since. The problem is in the registration UNC and gateway addresses.

**sj3ff** · 03-26-2009, 08:25 PM

Thanks for the update, I will have to contact them tomorrow and see if I can weasel my way past first level support...

**I8UB4** · 03-27-2009, 12:15 AM

Downloaded Pandora Radio a few minutes ago. It wouldn't log in, so I deleted the app. 8900 required a re-boot to delete the app. When the phone re-booted, it connected to UMA.

I have no idea why. I had done multiple battery pulls that didn't help. I've spent days trying to figure this out and then it just randomly fixed itself. Hmmm.

Who knows... I'll see if the UMA continues to work over time.

**Troyr** · 06-22-2009, 09:38 AM

I am having a similar situation as those above but with a twist. I am using a Linksys/Cisco WRT110 which (depending on the forum) has or doesn't have known issues. Anyway, I have gone through 4 different technicians and every possible configuration on the wireless router and handset. I have spent a total of 10+ hours trying to get this configured properly and it just won't.

I have 2 problems.

The first, if I get this to find the wireless router I get a red dot and 3 red bars (full strength), however, it keeps dropping off the router's connection adn trying to find a cellular tower (there aren't any near my home) and will drop my connection and actually put either SOS or NO CONNECTION next to the wireless antenna icon on the handset. No one can explain why in the world it will drop from a full hitting signal from my router to a tower, or lack thereof, with no signal strength. (Yes, all settings have been verified and the router is not dropping connections, it is set to G ONLY and all the other trouble shooting that could be done).

The second issue is that if I leave the area and return, it takes forever to actually find the wireless signal and connect to it but once it does, refer back to the above.

Additionally, I have set the manage wi-fi connections to ONLY look for the router and unticked it to look up the T-Mobile server. This appears to be the only way to get this to work, but obviously, it is a constant pain to keep ticking/unticking this feature when I leave and return home. And then I run into the same problem as described in #2 above.

If anyone has experienced this, preferrably fixed this issue, or knows how to get around this issue, please email me or respond here.

Thank you,

Troy

**Fla State Fan** · 06-30-2009, 05:36 PM

I just got my 8900 and it would not connect so no UMA went though tech support two days and transferred to I think there top Blackberry support still no UMA did everything everyone did on here so they replaced the phone it would not read the SD card anyway until I put it in four times so a good ideal to replace it anyway. Ok new phone card worked first time still no UMA found this thread on google search after reading figured out how to get the read outs you where coming up with had and error code and no address no connection looked up the code and one option was IPSec setting in the router, I looked and found it under security VPN settings I had turned it off since I didn't use them for security not knowing fully what it was for, Turned it on and I now have UMA and the new right address you are showing. Don't know if this will help anybody but thought I would post it just in case.

**hobson911** · 07-03-2009, 05:38 PM

Originally Posted by Troyr

I am having a similar situation as those above but with a twist. I am using a Linksys/Cisco WRT110 which (depending on the forum) has or doesn't have known issues. Anyway, I have gone through 4 different technicians and every possible configuration on the wireless router and handset. I have spent a total of 10+ hours trying to get this configured properly and it just won't.

I have 2 problems.

The first, if I get this to find the wireless router I get a red dot and 3 red bars (full strength), however, it keeps dropping off the router's connection adn trying to find a cellular tower (there aren't any near my home) and will drop my connection and actually put either SOS or NO CONNECTION next to the wireless antenna icon on the handset. No one can explain why in the world it will drop from a full hitting signal from my router to a tower, or lack thereof, with no signal strength. (Yes, all settings have been verified and the router is not dropping connections, it is set to G ONLY and all the other trouble shooting that could be done).

The second issue is that if I leave the area and return, it takes forever to actually find the wireless signal and connect to it but once it does, refer back to the above.

Additionally, I have set the manage wi-fi connections to ONLY look for the router and unticked it to look up the T-Mobile server. This appears to be the only way to get this to work, but obviously, it is a constant pain to keep ticking/unticking this feature when I leave and return home. And then I run into the same problem as described in #2 above.

If anyone has experienced this, preferrably fixed this issue, or knows how to get around this issue, please email me or respond here.

Thank you,

Troy

I was having pretty much the same problem. I also have the Linksys/Cisco WRT-110. Changed all the settings I could on the router and it continued to drop the connection. I ended up as last effort upgrading the firmware on the router to the latest firmware version 1.0.05 and it connected right up and has kept the connection. I do not know if you tried the firmware upgrade or not but it worked for me.

**vsinc** · 07-09-2009, 03:44 PM

Originally Posted by I8UB4

How did you change the Serving UNC and Gateway address issued by T-Mobile?

The UNCS (UMA Network Controller) and SeGW (SEcurity GateWay) can be set through the escreens (Under Mobile Network > Utilities > Session Manager > UMA options). Getting access to the escreens is tricky but (still) possible but this is for a good reason - too many settings there that can really make your phone unusable (and un-fixable).

The servicing UNC and Gateway are assigned dynamically based on your location - the N?? and W?? are (approximate) degrees latitude and longitude of your (last) location. My guess is they use the last GSM tower you connected to to route to the the closest data center.

I am extremely happy with UMA - using it since it first offered. Problems have almost disappeared and I got used to the process of handover - just walk slowly when it's time for the transfer :-)