 |
 | Vonage Forum Menu |
| | |
| Vonage Forums |
|
|
| | | |
| Vonage In The News |
| | |
| Vonage Customer Reviews |
| | |
| |
Vonage Actually, changing the settings as suggested in the 2nd post of the thread is the
Actually, changing the settings as suggested in the 2nd post of the thread is the settings that will decrease security.
SIP is session initiation protocol, the protocol that Vonage (and many other Voip) providers use to set up calls. SPI is stateful packet inspection. It is a firewalling algorythem that attempts to match data to an existing session. It can be a problem if the processor in the router cannot keep up with the rate of data going through the router, as is often the case with consumer-grade equipment.
The second post of this thread suggests disabling endpoint filtering. What this means is that, once a port is opened, any foreign host can portentially send data into your network through that port. You probablly don't want that.
Application Layer Gateway attempts to make certain applications seem to not be behind network address translation by re-writing the packets that go through the router by replacing the private IP address with your ISP-assigned public IP address.
Why can this be a problem? If you see that the contact address in your packet is a private IP address, you then need to take additional steps to find the public IP address and port the packet came from. Otherwise, if the contact address is public, you should be able to send a response back to where the packet tells you to. Even though ALG makes it appear that the packet isn't coming through NAT, it really is. This is where it becomes a problem. Lets say for example your TA device picks UDP port 10050 to send and receive audio on. Your ALG enabled router changes the contact address in your packets. However, when the packet goes throgh the NAT, the packet really is sent out into the internet over, say, port 21037. The firewall then doesn't accept the response on anything other than port 21037. But your packets are now telling the other end to send the response to port 10050.
The result is that what you are expecting to receive back fails to get to you. With a Voip phone call, you have one (or no) way audio.
Read The Full Thread: Can''t Make Calls with PAP 2
• Here is my set up:
Linksys PAP2
DIR-655 Router
Comcast Cable
8K Down
• Well afterVonage could not fix the problem after hours of talking to them I decided
• I am having exactly the same problem starting today. My equipment and service
• Change the settings to "Endpoint Independent" for both UDP and TCP and now it works
• DIR-655 Router
Linksys PAP
Embarq DSL (6Mb/640Kb)
Problem started
• I've experienced the same situation here starting late last week. I was able to
• What hardware version and firmware version is your DIR-655?
Mine is:
Firmware
• Firmware: 1.11
Hardware Version: A2
I did go back to 1.10 when I was haivng
• Mine is the same as yours:
Firmware Version: 1.11
Hardware Version: A3
1.11
• I started having the same problem today, although I upgraded router last week
trekologer posted "Actually, changing the settings as suggested in the 2nd post of the thread is the" on 01/23/2008 |
|
|
| |
| Vonage Service Plans |
| | |
| Vonage VoIP Members |
| | |
| Vonage Stock Price |
|
Value: 1.75
Change:  +0.05
Up to 15 Minute Delay | | | |
| Site Search |
| | |
|
|
Vonage VoIP Phone Service is redefining communications by offering consumers
& small business VoIP Internet phones, an affordable alternative to traditional phone service.
The Vonage VoIP Forum Generated This Page In: 0.35 Seconds and 319 Pages In The Last 60 Seconds
The Vonage VoIP Forum
|
Members
New 
New Today 7
Yesterday 3
Total 64278
Who Is On Site
Visitors 179
Members 0
Total 179