{"id":7,"date":"2009-11-24T03:57:20","date_gmt":"2009-11-24T08:57:20","guid":{"rendered":"http:\/\/signaturewebmedia.com\/blog\/?p=7"},"modified":"2010-01-08T14:53:30","modified_gmt":"2010-01-08T19:53:30","slug":"t-mobile-uma-configurations-for-netgear-wpn824v3","status":"publish","type":"post","link":"http:\/\/signaturewebmedia.com\/blog\/7\/t-mobile-uma-configurations-for-netgear-wpn824v3\/","title":{"rendered":"T-mobile UMA Configurations for Netgear WPN824v3"},"content":{"rendered":"

<\/a><\/p>

Sometimes we visit the customer’s site and need to use our cell phones (Blackberry) to communicate with our office. And sometimes, we do not have cellular connections over there. That is why we depend on T-mobile’s hotsopt@home\/UMA connections.<\/p>\n

This time, I could not connect using the customer’s wifi connections… so I had to diagnose why.<\/p>\n

The UMA diagnostics code was W006.1. Basically it is not communicating with T-Mobile’s UMA related servers; however, the wifi connection is in “connected” status.<\/p>\n

Some website suggested that nslookup (IP look up for the internet address) needs to be resolved for punc.t-mobileuncs.com; however, in our office, this was not the necessity. Many websites suggested that the port 500 and 4500 needs to be opened. Well, they should not be blocked according to the client’s Netgear WPN824v3. But hey, let’s use the “port forwarding” feature for the device. Then the error code of the diag changed to the W004.1.<\/p>\n

Mmmm…. something is going on. A few websites suggests that I should not use WEP wifi protection and should choose other methods. OK, try PSK…. and not working. OK, how about no protection…. and it WORKS! Why?????<\/p>\n

It must be the router is blocking something. Making a long story short, you have to disable WMM (Wi-Fi Multi-media) and use QoS (Quality of Service) for port 500 and 4500. Then your UMA connection should work for this router.<\/p>\n","protected":false},"excerpt":{"rendered":"

Sometimes we visit the customer’s site and need to use our cell phones (Blackberry) to communicate with our office. And sometimes, we do not have cellular connections over there. That is why we depend on T-mobile’s hotsopt@home\/UMA connections.
\nThis time, I could not connect using the customer’s wifi connections… so I had to diagnose why.
\nThe UMA diagnostics code was W006.1. Basically it is not communicating with T-Mobile’s UMA related servers; however, the wifi connection is in “connected” status.
\nSome website suggested that nslookup (IP look up for the internet address) needs to be resolved for punc.t-mobileuncs.com; however, in our office, this was not the necessity. Many websites suggested that the port 500 and 4500 needs to be opened. Well, they should not be blocked according to the client’s Netgear WPN824v3. But hey, let’s use the “port forwarding” feature for the device. Then the error code of the diag changed to the W004.1.<\/p>\n

Mmmm…. something is going on. A few websites suggests that I should not use WEP wifi protection and should choose other methods. OK, try PSK…. and not working. OK, how about no protection…. and it WORKS! Why?????
\nIt must be the router is blocking something. Making a long story short, you have to disable WMM (Wi-Fi Multi-media) and use QoS (Quality of Service) for port 500 and 4500. Then your UMA connection should work for this router.<\/p>\n

\r\n\r\n<\/a><\/p>","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false},"categories":[13,4],"tags":[195,6,194,5],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/posts\/7"}],"collection":[{"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/comments?post=7"}],"version-history":[{"count":14,"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/posts\/7\/revisions"}],"predecessor-version":[{"id":65,"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/posts\/7\/revisions\/65"}],"wp:attachment":[{"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/media?parent=7"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/categories?post=7"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/signaturewebmedia.com\/blog\/wp-json\/wp\/v2\/tags?post=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}