View Single Post
Old 11-27-2007, 12:32 AM   #11 (permalink)
pyrosee
Thumbs Must Hurt
 
Join Date: Nov 2007
Location: Portland, Oregon
Model: 8320
PIN: N/A
Carrier: t-mobile
Posts: 73
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I agree that I shouldn't have to tweak the t-mo routers settings, but I wanted to be absolutely positive. I forwarded the ports to my blackberry IP. The exact ports I forget off the top of my head- I had read those in another thread about what ports UMA uses. I also had a dlink non-tmo router, then bought a linksys WRT 300N, and finally just got the t-mo router.

Yes, I did set up my 911 info.

I get dropped calls all the time when I pull up to a starbucks and I am on a call. Mostly when I am in a vehicle at a particular starbucks right on the corner and am at a stoplight. When I leave the stoplight it drops the call. When I am walking downtown and on a call, it's less of an issue; I think the phone has a little more time to react to the UMA to Mobile switch. When I leave the house I try and remember to change my settings to "mobile network preferred" just to avoid this. But I do depend on my UMA at home due to a weak signal.

I do power cycle that router frequently. In fact, I have made a habit of getting home and power cycling the modem, router, and then my phone when I am home for the evening.

I will say that I experience these issues less often with the t-mo router, but nonetheless, it's still happening.

I am really just thinking this is going to be resolved with a phone software update as they work these bugs out. I have done my part my reporting everything that has happened to t-mo. I hope it works better for all of us soon!

Quote:
Originally Posted by sgtcasey View Post
I had an issue recently with incoming calls over UMA going right to voicemail without ever ringing my 8320. Tested at home by placing my SIM card into a Nokia 6086, same thing. Went to a Border's nearby to test on their HotSpot and same thing (to rule out my home network, router, ISP).

Called into work and had them file a trouble ticket but the issue seemed to resolve itself. They're leaving the ticket open for 5 days and I test it several times per day when I can. If it happens again I'll call back in to report the issue.

If you're having an issue like this make sure to test at another location preferably a T-Mobile HotSpot to rule out issues that might be caused by your home network, router, or ISP.

You shouldn't have to tweak the T-Mobile router's out much since they're pre-configured to work with UMA so I'm not sure what ports you forwarded unless they have nothing to do with UMA.

Just to make sure but did you set up a valid E911 address on your T-Mobile.com account? It's something that is required by law that T-Mobile have on file and I suspect if it's not there you might have some UMA problems. At any rate, setting it up rules out one thing that might cause issues.

I'm using my 8320 with a Buffalo WHR-G125 router running DD-WRTv24 with, so far, no issues (other than the call to voicemail thing that seemed to fix itself). I don't have anything fancy set up on the router except QoS placing the 8320 as the priority device by MAC. I am also using Comcast as my ISP.

Something to keep in mind is a powercycle of the router if you continue to have issues. It couldn't hurt and based on my experiences with other Linksys routers it seemed to solve issues I'd have periodically when it came to plain old 'net access.

Dave
__________________
Blackberry 8320 4.2.2.180
Offline   Reply With Quote