| Author |
Message |
charast
Vonage Forum Associate


Joined: Sep 08, 2005
Posts: 10
|
i have my own website that I host on my own server in my home. I have cable internet and DynDNS to translate my DHCP address from my internet provider to my internal server.
here is how I have it set up currently: cable modem goes to the WAN port on the VoIP modem, the PC jack on the the back of the VoIP modem to the WAN port on my Linksys router. then I have the servers connected to the router. this is all configured as Vonage suggests in thier link here: http://www.vonage.com/help.php?article=61&category=39&nav=3
I am able to get my VoIP service, and I have full access to the internet from all stations (inlcuding the webserver).
also, my DynDNS client is getting the correct IP address populated to it.
however, I am unable to get any traffic thru to my website at all.
any ideas? |
|
|
|
|
 |
VonageTPA
Vonage Forum MVM


Joined: Jul 11, 2005
Posts: 1715
Location: Florida (usually)
|
Some internet providers intentionally block TCP/IP port 80 to prevent people from running web servers. Try using a different port and see what happens.
to access the website, you'll have to change your URL, so if you're using port 88, you'd have to type:
http://<myip>:88/ |
_________________ ISP: Varies depending where I'm at.
Vonage: Linksys RTP300
Router: IPCop 1.4.10
Phones: various
Total calls since Jul 24, 2005: 4,794 calls
Total Minutes since Jul 24, 2005: 25,552 minutes |
|
|
|
 |
david0434
Vonage Forum Associate


Joined: Jul 01, 2005
Posts: 18
Location: Northern New York
|
charast -- It is likely that your VoIP modem is not passing port 80 through to your router.
If you cannot configure your VoIP modem to forward port 80, then you will have to connect your router to follow the cable modem and connect the VoIP modem to a LAN port on your router, just as your computer is.
If you do that, in your router you should forwarding ports 5060-5061 and ports 10000-20000 to your VoIP modem. |
_________________ Joined Vonage June 2005 |
|
|
|
 |
charast
Vonage Forum Associate


Joined: Sep 08, 2005
Posts: 10
|
| VonageTPA wrote: |
Some internet providers intentionally block TCP/IP port 80 to prevent people from running web servers. Try using a different port and see what happens.
to access the website, you'll have to change your URL, so if you're using port 88, you'd have to type:
http://<myip>:88/ |
thanks.. I am aware of this and will test it again but I have not had problems in the past with my ISP blocking port 80 traffic.
| david0434 wrote: |
charast -- It is likely that your VoIP modem is not passing port 80 through to your router.
If you cannot configure your VoIP modem to forward port 80, then you will have to connect your router to follow the cable modem and connect the VoIP modem to a LAN port on your router, just as your computer is.
If you do that, in your router you should forwarding ports 5060-5061 and ports 10000-20000 to your VoIP modem. |
I supposedly can forward ports on my VoIP modem and have set that up but it still does not work. When I had my router in the line first, i could not get my VoIP modem to work even tho on the router, I set up the apprpriate ports to forward.... very strange. |
|
|
|
|
 |
charast
Vonage Forum Associate


Joined: Sep 08, 2005
Posts: 10
|
ok.. I got it working. I had to put the router in front of the phone adapter and set the phone adapter to have a static IP on my subnet.
for whatever reason, I just could not get the adapter to forward the packets to the router.... possibly I had a router loop and they were being dropped... strange.
the only issue now is that I cannot get to the config screen of the adapter (even tho it IS on the same subnet) but that really is not a big deal. |
|
|
|
|
 |
djino
Vonage Forum Senior


Joined: Mar 27, 2005
Posts: 110
Location: Ottawa, Canada
|
Chances are now you may be effected by QoS (Voice Quality) since your voip is behind your router. But But, you may not, or may not care.
So Goodluck  |
|
|
|
|
 |
Jeckler
Vonage Forum Associate


Joined: Apr 21, 2005
Posts: 20
|
I would guess that the reeason it didn't work is because you're double NAT'ing. Turn your other router into a switch. That's also the reason why you can't access the config pages with the way you have it setup now. |
|
|
|
|
 |
|
|