Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mykroft]

there was a 2.02NA that my router told me was released on 9/15/09 - I flashed it last night and am wathcing - my disconnects have gone down by 99%

[JeffInTx]

Thanks for the suggestions and ideas all.  I finally gave up and returned the DIR-825.  Voip never worked on it.

I was using 2.02NA firmware, still do not see any update to this version as of 9/20/09 for NA users.  Hardware was B1.

Regarding port forwarding and configuration for SIP, IAX, etc., I hardcoded the ATA's IP address, then tried a) setting port forwarding udp for 5060, 5061, and 5004-5012 to it, b) I tried putting the ATA in the DMZ, and c) I even tried both Port Forwarding and DMZ together.  Last, but not least, I let the Dlink support people access both my router and my ATA try any settings they wanted.   Btw, my ATA is SIP (Grandstream HT502) and the ports specified per my provider's tech support.  As I said before, even if the tech support guys missed something, I'd think that the DMZ would have opened everything up anyway.

I've moved to a different router now and all is working. 

Again, thanks to you all for the ideas and help.

[mykroft]

ya, upong getting a B1 version (A1 worked just fine - but had to RMA it because a flash update hosed it) and not my outbound MagicJack data is not being passed out port 5070.

I switch back to my old DI-624 and bewm - the MagicJack registers with no problem - and all without port forwarding.....

[mykroft]

so what router is everyone moving to that VoIP works on?  I have been a D-Link user for prob close to 10 years - am beginning to reconsider that decision.

[crimsondryad]

My SO fried the wireless networking on my DIR-655, which worked fine with Vonage.  I bought this one and hooked it up, nothing but problems since.

I upgraded the firmware to 2.02NA (per recommendations seen here), set the UDP port forwarding on 5004-5012, 5060-5061, and 10000-20000. 

The inbound was working ok...people would call and I could hear them, but they couldn't hear me.  I just looked at it AGAIN and noticed on QoS that the Auto pipe setting was displaying a throughput of 044kbps (ie, dial-up speed) even though I have a broadband Roadrunner connection.  So I disable the Auto setting and set it up for 512kbps, which is what it should be upstream at a minimum.  I called a friend and had him call me back, seems to be working.  But...it seemed like it was better a couple times before, so we'll have to wait and see.  But for those of you who are having issues, try that out.

The other issue I had was that although I had a Wireless N laptop adapter and it was reading speeds of 300Mbps, it couldn't keep the connection up for more than 30 seconds at a time.  I would've been in heaven if it could.  Instead, what I had to do was use my Wireless-G adapter, which connects rock solid almost all the time, but can only carry 54Mbps across the network.  *sigh* 

Anyone have comments on why that would be?  The router is in the kitchen and the lappy is in the living room, approximately 30-50 ft away.  There is a brick fireplace in the wall between them that I thought was potentially causing issues, but wouldn't my G adapter have the same kind of problems?

[osj]

Just to add, I am using a SIP phone (Siemens Gigaset S675IP) on by DIR-825 without any problem - but maybe I am using a different version and firmware than you are facing problems with:

Hardware Version: A1
Firmware Version: 1.12NA

To make SIP working I had to disabled the option "SIP" under "Application Level Gateway (ALG) Configuration" in "Firewall settings" under the "Advanced" menu.

I need no port forwarding or DMZ on my setup to get it working. The only problem I am facing is that after a restart of the DIR-825, I also need to restart my VoIP phone - else it cannot register.... however that is probably a bad implementation in the VoIP phone rather than a problem of the router.

Best regards...Ole

[maxim.krusina]

...
To make SIP working I had to disabled the option "SIP" under "Application Level Gateway (ALG) Configuration" in "Firewall settings" under the "Advanced" menu.
...

When I tried this solution, I cannot register at all. I also tried to turn off SPI, but without any result. In default state (SIP checked in ALG), I can connect to SIP Account but cannot make any calls. (Siemens SIP and X-Lite SW phone).

Anyway, guy at support line told me that there should be a new FW in cca two weeks. So I'll give last chance to DIR-825. IF upgrade will not solve SIP trouble, I'll change my device for older DIR-655, which we have at office and it works for a long time without any problems.

Hardware Version: B1
Firmware Version: 2.01EU

[Lucion]

I have come across a problem with this router also.  I don't own the router and I just happened to come across this thread after dealing with the problem a couple of weeks ago.  The firmware was 2.02

Here are a list of the setting I tried and the results.  I was able to get a wirecap setup to see what traffic was getting past the D Link and what wasn't.  By default the ATA uses 5060 for port 1 and 5061 for port 2

DMZ on
Port Forwarding none
Port triggering none
SPI Enabled
SIP ALG ON

Registration occurs the ports are being hashed though. 
Test call out no invite actually goes out but I can see a cancellation request.
Test call in I can see the invites coming to the D Link, there is a response back from the ATA, Once the 200ok is received from the ATA and RTP traffic should be initiated there is just port not reachable and dead air


DMZ ON
Port forwarding None
Port triggering None
SPI off
SIP ALG off

No registration at all after enabled syslog and looking over what is happening I can see the ATA is trying to send out registration but I don't see anything on a capture.

Port forwarding and triggering didn't change anything.   I confirmed that it isn't the ATA or the ISP blocking SIP traffic as it works behind a Linksys WRT54G, DIR 655 and it works in front of the router.  Also I set a keep alive stun on each attempt and I didn't see that on the capture at all.  Normally I have to disable the SIP ALG on a DIR router.  It was bizarre to see that disabling it prevented any SIP traffic from leaving the LAN.  That is a major issue though as if a customer decides that they don't want the router misshaping  or mangling the SIP traffic it shouldn't completely block it.

From my experience the DIR series is a great router much better and reliable that the DI series. 

[dm33]

I just bought a DIR-825 for its Qos facilities hoping to be able to make reliable high quality VOIP calls while heavily using the network for other purposes.

I "think" it has largely worked, however I am experiencing inconsistent behavior.

In particular, I had a situation where I could not get my Linksys PAP2 to register no matter what I tried anywhere. Repeated rebooting the PAP2 didn't fix it. I put in a QoS rule to make any communication from the ATA the highest priority (1).

Nothing worked. Finally, although it would mess up a long running backup to the network... I rebooted the DIR-825. Suddenly the PAP2 was able to connect.

Why was the DIR-825 blocking the PAP2's registration request? I had it working last night. Sometime during the day it had stopped working and would not reconnect.

This thread makes it sound like it could be a recurring problem with the 825. If so, it fails at the primary purpose for which I purchased it.

Somewhat unrelated... but I then switched back on "Automatic classification" within the QOS engine configuration. To my surprise, the 825 apparently crashed and spontaneously rebooted. While I was trying to reconnect my system with lots of held up traffic trying to restart, it crashed again!

Is there a crash log of some type that would be useful to DLink?

Since the second crash it hasn't crashed again, my PAP2 ATA is still connected, everything seems to be ok. But I don't have much confidence that it will stay that way.

[Cata]

I am having the same problem.

Hardware Version: B1
Firmware Version: 2.01EU

Would flashing the 2.00EU back help? Any other suggestions? Or should I just send the 825 back?

Thanks!

[rockinthesixstring]

I'm using a Trixbox PBX through my 825 with ZERO issues.  DO NOT USE DMZ... bad news and not needed.

[rockinthesixstring]

SIP means Session Initiation Protocol and is used for making voip calls over the internet. It uses port 506  and some other ports for setting up a call, and the create a speech channel on a different port. My problem is that a call setup is made (the called party is called, and I hear the ringtone), but the answer message never comes to my SIP phone. So, when the called party picks up the phone, that message has to be sent to the calling party, otherwise a call can never be made...

Is that a typo or is it something else?  SIP uses port 5060.

[rockinthesixstring]

Man I cringe every time I hear someone say that they are using the DMZ for their voip box.  This is unsecure ant totally unnecessary. 

Use the Virtual Machine (Port Forwarding does not work).  Open up port 5060 on your box, and if you need to use RTP servers, you'll also have to open up the RTP range... Don't quote me, but I think its 10000 - 20000.

I will admit that I had problems with Port Forwarding on my 825, but as I said, Virtual Machines worked fine.

My config...

DIR-825 for routing and gateway
Server 2003 to power DHCP and DNS
Many client pc's and media streamers
2 Linksys SPA-941 VoIP telephones

Entire system is working flawlessly.

[Cata]

I am not using DMZ. You can't specify a port range for Virtual Servers, so you have to use Port Forwarding.

What hardware and firmware version do you have on your DIR-825?

Is your external VOIP provider connecting you through SIP or something else?

Thanks!

[rockinthesixstring]

I am not using DMZ. You can't specify a port range for Virtual Servers, so you have to use Port Forwarding.

What hardware and firmware version do you have on your DIR-825?

Is your external VOIP provider connecting you through SIP or something else?

Thanks!

Do you require the use of RTP?  If not, then you prolly don't need a range.  I use CallCentric which doesn't require RTP.  They connect directly to my PBX.