Sign up
Vonage Forum Menu
The Vonage Forums
Vonage VoIP Forum
Vonage Forum Archive
Vonage Canada
Vonage UK
Vonage Stock
Fax, Tivo & Alarms
Hard Wiring
Number Transfer
V-Phone & SoftPhone
VoIP Feature Request
Vonage TV Ads
International Rates
Forum Suggestions
Report a Bug
The Cafeteria
Forums Archive
All Vonage News
Vonage In The News
Press Releases
Forum Digest
News Archives
Vonage Sign Up Info
Vonage Features
Vonage Area Codes
Vonage FAQ
Vonage Reviews
VoIP Speed Test
Vonage Toolbar
Network Setup
Wiring & Installation
Vonage 911
Business Account
VoIP Acronyms
VoIP Advertising
Wi-Fi Phone
Contact Support
Member Registration
Member Login
Member List
Your Account
Private Message
Forum Faqs
Recommend Us
Website Feedback
Forum Syndication
Forum Newsletter
Search Using Google
Search Forums
Search News
Forum Speed Dial
Vonage Forum
Forum Community
The Vonage Forums
Vonage VoIP Forum
Forum Archive
Vonage Canada
Vonage UK
Vonage Stock
Fax, Tivo & Alarms
Hard Wiring
Number Transfer
V-Phone & SoftPhone
Feature Request
Vonage On TV
International Rates
Forum Suggestions
Report A Bug
The Cafeteria
All Archives
Vonage News
All Vonage News
In The News
Press Releases
Forum Digest
News Archive
Vonage Information
Sign Up Info
Vonage Features
Area Codes
Vonage FAQ
Vonage Reviews
VoIP Speed Test
Vonage Toolbar
Network Setup
Wiring & Installation
Vonage 911
Business Account
VoIP Acronyms
VoIP Advertising
Wi-Fi Phone
Contact Support
Member Services
Registration
Member Login
Member List
Your Account
Private Messages
Forum Faq's
Recommend Us
Website Feedback
RSS Syndication
Forum Newsletter
Search
Search Using Google
Search Forums
Search News
Vonage Forums
Can't Make Calls with PAP 2
Goto page
Previous
1
,
2
,
3
Next
Vonage® VoIP Forum - Vonage News, Reviews And Discussion
»
Vonage Forum Archive
Author
Message
hayestrio
New Forum Member
Joined: Jan 22, 2008
Posts: 2
Posted:
Tue Jan 22, 2008 1:01 am
Post subject:
I started having the same problem today, although I upgraded router last week with NO problems until now. Spent an hour with
Vonage
tech support and got nowhere. Finally a supervisor told me they had recieved several other calls from customers complaining about the same thing, and they all seemed to be using a dlink router.
Tried changing the TPC & UDP settings mentioned in this post and IT WORKED! ...Thanks guys!!!!!
DLINK DIR 655
H/W: A3
F/W: 1.10 (UPGRADED TO 1.11)
phoquenut
New Forum Member
Joined: Jun 18, 2006
Posts: 6
Posted:
Tue Jan 22, 2008 7:04 am
Post subject: DGL4300 - Same issue as yours...
Same fix.
Thanks for reporting it!
NEWCASTLE
Full Forum Member
Joined: Mar 04, 2006
Posts: 62
Posted:
Tue Jan 22, 2008 11:34 am
Post subject:
I've got the following, and those firewall changes fixed my issue.
Hardware Version: A1/A2
Firmware Version: 1.11
Thanks Matrix0785 for pointing me to this thread!
DannyH
New Forum Member
Joined: Jan 22, 2008
Posts: 2
Posted:
Tue Jan 22, 2008 1:31 pm
Post subject:
Thanks much, fixed my issue as well........
H/W: A1/A2
F/W: 1.11
Dan
trekologer
Vonage Forum Evangelist
Joined: Dec 04, 2005
Posts: 350
Posted:
Tue Jan 22, 2008 10:28 pm
Post subject:
Newer D-Link routers have a "feature" called Application Layer Gateway. It basiclly re-writes the packets of vertain protocols to make it appear that its not coming from behind a router. But you still are behind a router and special handling is needed for streaming data connections.
Now here is a problem. Some models (DI-625) have it but aren't documented and cannot be disabled. Others have it (DIR-655) but depending on the firmware version can't be disabled unless you upgrade the firmware to the latest version. Note that if you need to upgrade your firmware, you should make a note of any settings you have in the router, such as your connection type (if you use PPPoE, for example) and wireless security settings as firmware updates tend to wipe out settings. Yay D-Link!
Anyway, go into the Advanced section and then Firewall. Uncheck SIP. Save settings. Reboot.
miked2
Vonage Forum Senior
Joined: Sep 15, 2006
Posts: 94
Posted:
Wed Jan 23, 2008 6:20 pm
Post subject:
Some thoughts:
(1) I wouldn't uncheck the SIP box, as that provides stateful inspection of packets -- a very useful firewall tool. YOu'll decrease how well the router works as a firewall by unchecking this box.
(2) I had the same problem as reported in this post, although before I found this post, I contacted
Vonage
. They "refreshed some settings" for my device, I did a hard reboot of the adapter, and the problem went away. So to some extent,
Vonage
can correct this problem on their end.
FWIW, I've had to contact
Vonage
tech support twice in the past 90 days (this issue, and also one line wouldn't "undo" it's call forwarding), and had great success on both counts. This last time I did everything via email, and within 48 hours the problem was resolved. The first time I called up tech support. The gentleman in India was very nice, and had me try certain things. When that didn't work, he sent me to New Jersey. This guy was ruder (it was 3 AM his time on Sat night), but got my problem fixed right away.
DentalRep
Vonage Forum Senior
Joined: Feb 15, 2005
Posts: 85
Posted:
Wed Jan 23, 2008 6:28 pm
Post subject:
miked2 wrote:
Some thoughts:
(1) I wouldn't uncheck the SIP box, as that provides stateful inspection of packets -- a very useful firewall tool. YOu'll decrease how well the router works as a firewall by unchecking this box.
(2) I had the same problem as reported in this post, although before I found this post, I contacted
Vonage
. They "refreshed some settings" for my device, I did a hard reboot of the adapter, and the problem went away. So to some extent,
Vonage
can correct this problem on their end.
FWIW, I've had to contact
Vonage
tech support twice in the past 90 days (this issue, and also one line wouldn't "undo" it's call forwarding), and had great success on both counts. This last time I did everything via email, and within 48 hours the problem was resolved. The first time I called up tech support. The gentleman in India was very nice, and had me try certain things. When that didn't work, he sent me to New Jersey. This guy was ruder (it was 3 AM his time on Sat night), but got my problem fixed right away.
You don't need to uncheck the "SPI" selection to fix this issue. Only change the settings I mentioned in the earlier posts.
_________________
Keith Wilson
trekologer
Vonage Forum Evangelist
Joined: Dec 04, 2005
Posts: 350
Posted:
Wed Jan 23, 2008 8:48 pm
Post subject:
miked2 wrote:
Some thoughts:
(1) I wouldn't uncheck the SIP box, as that provides stateful inspection of packets -- a very useful firewall tool. YOu'll decrease how well the router works as a firewall by unchecking this box.
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.
miked2
Vonage Forum Senior
Joined: Sep 15, 2006
Posts: 94
Posted:
Wed Jan 23, 2008 11:41 pm
Post subject:
Ah, very interesting! I think I'm going to reset the settings to what they were before, as
Vonage
got it working for me.
NEWCASTLE
Full Forum Member
Joined: Mar 04, 2006
Posts: 62
Posted:
Fri Jan 25, 2008 7:34 pm
Post subject:
What exactly did
Vonage
do for you to get it working? I'm still confused as to why DIR-655 users suddenly started having issues. Did
Vonage
change something on their end?
Display posts from previous:
All Posts
1 Day
7 Days
2 Weeks
1 Month
3 Months
6 Months
1 Year
Oldest First
Newest First
Vonage® VoIP Forum - Vonage News, Reviews And Discussion
»
Vonage Forum Archive
Goto page
Previous
1
,
2
,
3
Next
Jump to:
Select a forum
Vonage® VoIP Forums
----------------
Vonage
Vonage Forum Archive
Vonage Canada
Vonage UK
Vonage Stock
Fax - Tivo - Alarms
Hard Wiring - Installation
LNP – Local Number Portability
Vonage V-Phone & SoftPhone
VoIP Feature Wish List
Vonage TV Commercials
International Rates
Forum Suggestions - Open Topics
----------------
The Cafeteria - Any Non Vonage Topic
Forum Suggestions - Comments
Report A Forum Bug
You
cannot
post new topics in this forum
You
cannot
reply to topics in this forum
You
cannot
edit your posts in this forum
You
cannot
delete your posts in this forum
You
cannot
vote in polls in this forum
All times are GMT - 5 Hours