rt31p2 T-1 multiple server LAN

Posts: 10 · Vonage Forum Associate Joined: Jul 09, 2005 Posts: 10

I have a T-1 with a Class C block (255 static IPs). On the LAN there are 4 Web servers and 3 other computers that are accessed from the internet on other protocols. There is no DHCP server on the LAN, everything is static.

I signed up for Small Business Unlimited, with a toll-free number added, several days ago. We've been forwarding the number(S) since then to an existing phone, no problems.

Today I got the rt31p2 and plugged it into the primary 16-port switch that is behind the Cisco 1720 T-1 router. Configured it with an available static IP. Wouldn't work (meaning voice status was disconnected, and no phone lights or dial tone).

A couple of hours with level 1 (where they had me do hard and soft resets, reconfigure the WAN, etc, all the normal stuff they have to do) before moving to level 2. I opened up port 8080 in the router for the rt31p2's IP, and the tech was able to log in to it. Never found anything wrong, but at their end they could see continuous connection attempts timing out.

Suggestions were two: bad rt31p2, or problems getting the voice connection through the switch (SMC 16-port unmanaged 10/100). They wanted me to put the rt31p2 between the router and the switch, but I balked at that for now.

Brought the rt31p2 home and plugged it into my home satellite internet. It was operational both behind my normal wireless router and in front of it, but it worked best as the first device and with bandwidth saver cut down to 30K. Had a couple of long calls that went fine.

So, the rt31p2 is fine.

Now after all that, here's my question: If I put the rt31p2 behind the T-1 router ahead of the switch, is there any way to figure it to forward all inbound connections without regard to destination IP? Running DMZ to a single computer isn't going to work, and neither is specific port-forwarding because I need multiple port 80s for example.

If that's not possible, any suggestions for a switch that is likely to work ahead of the rt31p2, or why the existing switch does not?

Posts: 10 · Vonage Forum Associate Joined: Jul 09, 2005 Posts: 10

Thanks to some helpful folks in the Voip forum at BroadbandReports.com I'm now up and running. The problem was the Cisco router blocking required ports, and no problems at all with the switch.

Both first and second-level support assured me repeatedly that I did not need to open specific ports for the rt31p2. That shows that, despite lengthy discussions of my network topography, they didn't recognise the difference between using a home Cable or DSL router vs using a Cisco T-1 router. On the home boxes, return on established connections is always open; on the Cisco nothing is open unless explicitly allowed, and the only rule for established connections was applied strictly to TCP.

The answer was to open up inbound UDP to the Linksys IP, and the phones came on almost instantly.

Posts: 148 · Vonage Forum Senior Joined: Feb 28, 2005 Posts: 148

Congrats, and now enjoy the lower phone bills! Very Happy