Connecting T-Mobile @Home Router to 3600HGV Gateway

[barrance]

I have the old discontinued T-Mobile @Home (VOIP) service.  I was recently upgraded to U-verse internet from DSL and would like to continue using the @Home service.  Since the 3600HGV gateway is both the modem and router, I simply need to feed an internet signal to to the @Home router, which is a Linksys WRTU54G-TM.  There is supposed to be a blue light on if everything works properly.

At first, after getting my U-verse internet set up, all I did was plug a cable from one of my internet ports from the Gateway to the @Home "internet" plug.  This did not work.  The Gateway didn't even recognize it as a connected device.  After doing some research, some folks said I was supposed to turn off DHCP on the WRTU54 and set it to Bridge mode.  After doing this, the Gateway recognized it as a connected device, but still no blue light, no dial tone. 

Can anyone tell me what I'm doing wrong?

[JefferMC ACE - Professor]

Does the @Home router use the SIP protocol?  The U-verse RG has been known to block those ports (for its own VOIP use).  I'm not sure, but you might be able to work around this issue by assigning your @home device into the DMZplus zone from the RG.

[barrance]

Any clue how to do that exactly?  After I set the WRT54 to bridge mode, these two items showed up as being connected to Port 2 on the Gateway:

NP-12C1AN092111

COM-MID1

I know you this is in the firewall settings, but I don't think I know how to do it exactly.

[gregzoll_1]

If @Home is discontinued, why are you trying to set it up? If you are trying to use the old router as a Wireless AP, you can do that, by connecting to the LAN jack on the back, and turning off DHCP. Set it for something like 192.168.2.254 as a STATIC IP in the Linksys.

[barrance]

Well, to clarify, @Home was discontinued as in no longer being offered, but they were allowing customers that had it to keep on using it.  I think I have it set up exactly as you describe it so it is working as a Wireless AP, but it doesn't seem to allow the phone line to turn on.  I don't think I set a static IP for the Linksys though... hmm...

[gregzoll_1]

Due to what JefferMC stated, only thing you can use that Linksys for, is a AP, not for TMobile's VoIP service. You could try placing it into a DMZ for router behind router. You will have to connect from a LAN on the RG, to the WAN on the Linksys.

[barrance]

Well, it looks like I figured it out, although I'm not actually sure what I did right.  First of all, I couldn't access the WRT54 anymore after switching it to bridge mode, so I had to do a hard reset (maybe this was it?).  After that, I plugged a cable from the computer to the WRT54 LAN and logged in.  From the default settings, he only thing I did after that was change the local IP to 192.168.2.1 and I disabled DHCP (I think this was probably it).  I then unplugged the LAN connection to the computer and connected the WRT54 WAN to Gateway LAN.  From the Gateway settings, a new "unknown" device showed up through the connected port.  As I was trying to figure out how to access the WRT54, I looked up and sure enough, the blue light signaling VOIP was active on the WRT. 

Bottom line is, I got the @Home to work, even though I'm not sure what I did.  Normally, this would bother me, but at this point, I'm just glad the phone is working.  Thanks everybody for the help.

[dhascall ACE - Master]

Just curious: Even if the @Home (paid) service is no more, are they letting you make free VOIP calls over it?  If so, I see why you would want to keep it and I don't blame you!

I beta tested both the Router and the @Home service for T-Mo aboit 7 years ago. 

I had no idea that the @Home service was even sick, let alone "dead." Lol.