[200KIAS]

We have two 8320's and both quit working in two places, office and home. T-mobile tech blames our router. We have very different routers in each location. We are getting error 006.2 and 006.3 on each device.

[silvervic02]

I'm having the same issue down here in Atlanta. UMA's been working fine until now...Wake up this morning, and no UMA... Keep getting those same error codes.. The device is trying to connect, but no success. I called T-Mo CS... First Rep did the same thing, blamed my non T-Mo router.. (I have a NetGear btw). Called back for another rep who was more knowledgeable and helpful. After doing some tweaks to the device, he found out that there are some UMA outages over the US... I'm guessing this is the culprit.. However, I am not still not satisfied... Anyone else having these issuses?

Thanks!

[TroyDBrown]

I know TMO has been having a few issues since yesterday. I keep getting lowercase uma.

[newberry52]

I am glad to see that I am not alone! I have been on the phone with three techs today and nothing! I have wiped my phone, checked my d-Link router settings, reset, and more various times. I am in Atlanta, too. My husband has a Samsung Katalyst and it is working fine on UMA, but not my BB. I am getting the W006.2 error also which indicates an ISP or T-Mobile Network problem, but at least the last tech is saying that maybe it's my phone. I hope this gets resolved quickly.

[ms_ccr]

I find this very interesting. Wish I had looked here before I called T-Mobile. I spend two hours on the phone with T-Mobile this afternoon and they never mentioned possible outages. I am not using a T-Mobile supported router (Netgear) but it was working fine for a month, then todayxxx8230; They did ask me to go to a T-Mobile store to see if I can connect to the UMA server from the store router. If I can then the issue is my home routerxxx8230;

[TroyDBrown]

Originally Posted by ms_ccr

I find this very interesting. Wish I had looked here before I called T-Mobile. I spend two hours on the phone with T-Mobile this afternoon and they never mentioned possible outages. I am not using a T-Mobile supported router (Netgear) but it was working fine for a month, then today… They did ask me to go to a T-Mobile store to see if I can connect to the UMA server from the store router. If I can then the issue is my home router…

You may want to wait a day for the issue to clear before doing the Starbucks / TMO store thing.

[200KIAS]

Originally Posted by troydbrown

You may want to wait a day for the issue to clear before doing the Starbucks / TMO store thing.

I did go to a T-mo store and it does work there. This looks like an issue where T-mo changed something either knowingly or not but the change has interrupted @home service. I know I did not do anything to ALL of my routers over night and mysteriously we are all having the same problem. It is really frustrating!

[newberry52]

I went to a Starbucks, too, and within 5 minutes was talking over UMA to my husband who was sitting outside the store. Got back home and the problem persists. It is frustrating!

[silvervic02]

So it works at Starbucks and T-Mo stores?? One of the reps suggested that I go to the Starbucks and test it out, but just haven't had a chance to leave work! Another rep suggested that I reload all my software... Any ideas on that one? Not too happy at the moment

Thanks all..

[newberry52]

Reloaded software, no change. Now not even my husband's Samsung is working on the home network.

[silvervic02]

Thanks for the heads up newberry52... Will not go through the software reload... Any thoughts on next steps..

[jibi]

By the way, mine isn't working tonight, either. This is just south of Atlanta.

[hdawg]

Boston, MA ... its working perfect; all day.

[jibi]

...i find it odd that 5 of the people in this thread are in Georgia.

[kadriasif]

this mornning i noticed that no uma network called T mobile no luck went to store works fine bought new router still same no uma bb 8120 gets on wifi can surf net but no uma for voice iam also in atlanta dont know it is bellsouth or T mobile outages i have nokia 6086 same issue so for sure it is not phone or routers

[jnelson2000]

Cannot connect here in Chicago area. UMA shows available but not connected.

[silvervic02]

Hmm... so it seems us GA folks and our friend from Chicago are out of luck on this one.. Not a handset issue, not a router issue.. a T-Mo issue it seems.. Waiting patiently for them to fix is not one of my key attributes...

Thanks to all who chimed in.. Who knows, with these crazy storms tonight, might not even have Edge tomo lol.. j/k...

[sgtcasey]

Working fine in Albuquerque, NM today. I just made a couple test calls to make sure.

Dave

[bberry8320]

I'm in metro-Atlanta as well and my UMA is down. After going through a series of checks with TMO, as well as going to a hot-spot, it still isn't working. I have a TMO router so can't blame that. TMO is swapping out my phone because of this. I find it very, very interesting though that most of the posts regarding this are from people in Georgia, although TMO has checked and has not reported any problems with this area. I have been having A LOT of problems in addition to UMA with coverage in general from TMO here in Atlanta within the last few months.

Anyone else?

[sgtcasey]

Originally Posted by bberry8320

I'm in metro-Atlanta as well and my UMA is down. After going through a series of checks with TMO, as well as going to a hot-spot, it still isn't working. I have a TMO router so can't blame that. TMO is swapping out my phone because of this. I find it very, very interesting though that most of the posts regarding this are from people in Georgia, although TMO has checked and has not reported any problems with this area. I have been having A LOT of problems in addition to UMA with coverage in general from TMO here in Atlanta within the last few months.

Anyone else?

Wow, a handset exchange for a UMA outage? That rep did not do their job at all and took the "easy" way out to get you off the phone. If there are no confirmed issues of an outage the rep should have filed a trouble ticket to get this on the radar of the network folks.

Did the rep at least have you reload the OS on the device before doing the exchange?

Dave