Want a feedback please!!!

**Russell** · 01-12-2010 08:40 PM

Originally Posted by voip123

I started frustrating since day 5 after I signed up for the service. At least once per day the adapter doesn't work for around 15 minutes. Sometimes 2 or 3 times per day. It will back on.

I checked everyone's feed back. None of you is using the WRT54GS. Sounds like the router doesn't like its Linksys cousin - RT31P2.

At the moment, I am writing this post. The Line1 light is out.

Have you tried with the router next to your modem? Does that work fine? If yes, then you really can't fault VOIPo.

**dteague** · 01-13-2010 06:56 AM

Originally Posted by ctaranto

What firmware are you running on the WRT54GS?

I know it might be a pain, but did you try hooking things as described in my post? I'd be curious if that resolved your issue.

I have a WRT54G2 running dd-wrt, and I have had this issue when the TA was on either side of it. For no reason, the lights will go out for Lines 1 & 2, and I have no dialtone. If the TA is plugged into the cable modem, and the WRT54G2 on the other side, if I have no lights on line 1 & 2, I have no internet access on any of my computers. When I put the TA off the WRT54G2, when it dies, it only takes down the phones as nothing is down line of it.

VoIPo has replaced the TA, and it has made no difference. I did notice their was a later firmware for the TA, and asked VoIPo about it, but they did not thing that would resolve the issue. It seems to be something in the TA that is having the problems.

Right now, I have the TA off the WRT54G2, in the DMZ, ports forwarded, on a static IP address (NAT). Like I have said, it will work fine, then all of a sudden, no Line 1/Line 2 lights and no dialtone.

My wife could care less who we use, as long as "There is dialtone when she picks it up, and people can call us." VoIPo is not making my choice to move to them easy on either one of those points.

**Russell** · 01-13-2010 07:45 AM

Originally Posted by dteague

I have a WRT54G2 running dd-wrt, and I have had this issue when the TA was on either side of it. For no reason, the lights will go out for Lines 1 & 2, and I have no dialtone. If the TA is plugged into the cable modem, and the WRT54G2 on the other side, if I have no lights on line 1 & 2, I have no internet access on any of my computers. When I put the TA off the WRT54G2, when it dies, it only takes down the phones as nothing is down line of it.

VoIPo has replaced the TA, and it has made no difference. I did notice their was a later firmware for the TA, and asked VoIPo about it, but they did not thing that would resolve the issue. It seems to be something in the TA that is having the problems.

Right now, I have the TA off the WRT54G2, in the DMZ, ports forwarded, on a static IP address (NAT). Like I have said, it will work fine, then all of a sudden, no Line 1/Line 2 lights and no dialtone.

My wife could care less who we use, as long as "There is dialtone when she picks it up, and people can call us." VoIPo is not making my choice to move to them easy on either one of those points.

So how does your service get restored when this happens. Do you power-cycle the ATA?

**dteague** · 01-13-2010 07:57 AM

Originally Posted by Russell

So how does your service get restored when this happens. Do you power-cycle the ATA?

Yes, As soon as I power-cycle the RT31P2 and it "boots", I have dialtone and I can make/receive calls.

**ctaranto** · 01-13-2010 08:14 AM

dteague,

If you're willing to experiment, would you be willing to hook things up the way I described in the thread http://forums.voipo.com/showthread.php?t=1919 ?

I'd like for someone else to try it out to see if my case was just pure luck, or is there something "special" about bypassing the direct LAN to WAN connection from the WRT to RT.

/c

**dteague** · 01-13-2010 08:40 AM

Originally Posted by ctaranto

If you're willing to experiment, would you be willing to hook things up the way I described in the thread http://forums.voipo.com/showthread.php?t=1919 ?

I'd like for someone else to try it out to see if my case was just pure luck, or is there something "special" about bypassing the direct LAN to WAN connection from the WRT to RT.

I will try it and see if it makes any difference. I used to do networking for a living, and just having a hard time wrapping my head around how this will solve anything as it seems to be adding a hop to all transmissions (abit it an out of the WAN to the LAN port on the RT31P2 and then to the WRT54G2... But stranger things have happened... If it does work, then I start thinking more twords it being a firmware issue on RT31P2.

**ctaranto** · 01-13-2010 09:33 AM

I'm guessing (and purely a guess) that coming in the LAN of the RT is different, either NAT, Firewall, or otherwise, than coming in through the WAN. Once in the LAN of the RT, going out the WAN is transparent. I am knowledgeable about networking, but by no means a pro. A side benefit of doing it this way is one can "manage" the RT through a normal IP address since it's on the same subnet.

My RT is running 1.25.00.

/c

**voxabox** · 01-13-2010 10:42 AM

Router: WRT54GS (tomato 1.27)
ATA: Linksys/Sipura SPA1001
ISP: Comcast

Cable Modem -> Router -> ATA (UPS'ed)

I'm a grandfathered BYOD user
My ATA never reboot unless I tell it to

Cheers,
-v

**dteague** · 01-13-2010 11:30 AM

Originally Posted by ctaranto

I'm guessing (and purely a guess) that coming in the LAN of the RT is different, either NAT, Firewall, or otherwise, than coming in through the WAN. Once in the LAN of the RT, going out the WAN is transparent. I am knowledgeable about networking, but by no means a pro. A side benefit of doing it this way is one can "manage" the RT through a normal IP address since it's on the same subnet.

My RT is running 1.25.00.

I'll have to check and see what version my RT is running. I know both of the ones VoIPo sent me are running the same version and when I checked there was a later version of the firmware out there.

I'm able to manage my RT that is plugged into my WAN port today. I just go out to http://192.168.15.2:999 (or is it 4 9's?) and it brings up the login popup and then I'm in.

I'll let you know version and if I get it to work.

Since it is not an everyday thing for me, I may not notice if it doesn't fall off. If it works, even tho it is not "clean", I'd be able to live with it.

**ctaranto** · 01-13-2010 11:55 AM

I was referring to being able to manage it without using port numbers. See? You can't even remember what the port was!.

Latest firmware for the RT is 1.30.07, dated (gasp) 12/20/06. The 1.25.00 firmware is from 2004 (December 1 to be exact). I asked VOIPo if I could upgrade. They said that they ship the routers with the support firmware level.

From work, I SSH (using autossh, and not port 22) into my WRT and set up a tunnel (one could also use the very excellent Tunnelier on Windows). I use proxy forwarding, using FoxyProxy to manage my FireFox connections (internal to work or external), and all external traffic is being tunneled to my home router, which then relays back all internet traffic. This way all external traffic, including DNS requests, is fully encrypted from prying eyes in IT (including IM messages).

I've use wireshark to verify the traffic, and boy is it encrypted.

This also allows me to directly connect to my home routers/adapters/PC from work. I can monitor the status of the RT (and WRT) from the comfort of my office chair.

/c