Print

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

[tomek]

Same problem here. I just installed the DIR-825 in my configuration and CANNOT get VOIP to work at all. My internet provider is Verizon Fios (fiber optics) and my VOIP is Nextiva. Nextiva second level support technician spent almost 3 hours with me to try to get it work - NO LUCK. I had no problem with this VOIP when I used the Linksys router. Does anyone can suggest soemthing?

[Cees]

Does anyone can suggest soemthing?

My suggestion: Please contact Dlink and ask for support,  refer to this topic.  If more people complain, maybe they understand that something is broken in the 2.01/2.02 firmware.

[JeffInTx]

Posting reviews/comments on other sites, like where you bought it, might also help inspire addressing of the issues.  At the very least, it will let others know before they buy one that, despite the ads touting this router for people who use VOIP, many people are having trouble with it.

[ChickenMan]

Found some interesting stuff on SIP for VoIP....
http://www.fredshack.com/docs/sip.html
http://www.voip-info.org/wiki/view/SIP
http://www.voip-info.org/wiki/view/NAT+and+VOIP

[Cees]

Found some interesting stuff on SIP for VoIP....
http://www.fredshack.com/docs/sip.html
http://www.voip-info.org/wiki/view/SIP
http://www.voip-info.org/wiki/view/NAT+and+VOIP

All this information is well known here, but useful for others.  I am using SIP/VOIP for many years here with other routers and I know what to do with portforwarding.  That is not the problem here.  The firewall just blocks the last part of the call-setup (the audio-channel) even when using DMZ, while it should pass everything unchanged in DMZ mode. 

As it is reported that the problem does not appear in firmware 2.00 and does in 2.01 and up, there must be something broken in the firmware.

Until now no reaction from D-Link.  Not on the 'case' I have opened and also not on email I have sent later.... 

[tomek]

Finally I have some answers... nothing good though. After spending hours with D-Link support (I got to the highest level they have - Product Specialist) I was told the D-Link is aware of the problem in the 2.02NA firmware and it is working on the solution. They were not able to provide me with any dates or even estimates.

Tomek

[leonhugens]

I worked with Dlink support for over 2.5 hours, letting them drive any config changes they wanted to either my router or ATA.  In the end, they sent an email, "I believe the issue has to do with the service provider configurations."  I responded that the service has needs only ports 5060, 5061, and 5004-5012 all udp protocol.  Shouldn't that all be handled okay if the ATA is in the DMZ?  Just in case, I tried adding Port Forwarding for each port as well.  Still nothing.   I haven't heard back in 10 days, but hope they're still checking. 

Meanwhile, the comment above about VOIP stopping with the EU upgrade is interesting.  Does anyone have 2.00NA firmware that we could test?  I upgraded my router to the latest, 2.02NA before trying anything and now don't have 2.00NA to fall back to.

Cees supplied it to me via a different post:
It is on the ftp site of dlink-uk:
ftp://ftp.dlink.co.uk/dir_products/dir-825/dir-825_fw_2-00_rev_B1.zip

[flg]

I’ve bad news for you guys:

I’m probably one of the persons that made them take this issue seriously, as I spent some time with tech support a couple of days ago, with no help whatsoever from them.

Anyway, after tech support assured me that I could not downgrade, and that the old version was no longer available (we know better now), I exchanged my upgraded 825 for another one with the original firmware 2.00NA. Guess what, it also did not work with SIP/VOIP.

Now, I did not try the European version available in the UK D-Link ftp site, because I also returned the exchanged router. So, that is our last hope before they come out with a new firmware that fixes this.

Has anyone already tried this 2.00EU version?

[JernWilly]

Yes. When I bought mine back in June, it was delivered with 2.00EU.
VoIP didn't work.....

JernWilly

[uniuk2000]

Yes. When I bought mine back in June, it was delivered with 2.00EU.
VoIP didn't work.....

JernWilly

Saying that, my router is running 2.00EU and working fine with VOIP. It's strange how some people are affected and others not.
The only time VOIP didn't work on mine was when I upgraded to 2.01 EU, it was soon downgraded back down again I tell you.

[tafkap]

EU Version, went back from 2.02 to 2.00 and it KINDA works.
I can make calls, receive calls and be heard by the other side however i can NOT hear the other person.
I created forwards for ports 5004(RTP), 5060(SIP) and 10000(STUN).

Any ideas what I'm missing?

[jello]

I have the A1 1.01 firmware. I use OOMA w/ no issues.

[jooel999]

After I filled out the "error report" on D-Links homepage I received an url for an updated firmware. After uploading to my DIR-825, SIP seems to work just fine, no port forwarding or DMZ necessary. The new firmware contain a "beta01" but after updating my DIR-825 still reports having the 2.01EU version. I have the B1 hardware version.

[mykroft]

I worked with Dlink support for over 2.5 hours, letting them drive any config changes they wanted to either my router or ATA.  In the end, they sent an email, "I believe the issue has to do with the service provider configurations."  I responded that the service has needs only ports 5060, 5061, and 5004-5012 all udp protocol.  Shouldn't that all be handled okay if the ATA is in the DMZ?  Just in case, I tried adding Port Forwarding for each port as well.  Still nothing.   I haven't heard back in 10 days, but hope they're still checking. 

Meanwhile, the comment above about VOIP stopping with the EU upgrade is interesting.  Does anyone have 2.00NA firmware that we could test?  I upgraded my router to the latest, 2.02NA before trying anything and now don't have 2.00NA to fall back to.

ATAs are either SIP or IAX - 99% of them are SIP, SIP uses port 5060 by default and a range of 10000-25000 for the RTP protocal.  If both of these ranges are not open, you can make calls just fine, but receiving them will be hit/miss.  Either configure your ATA to use a STUN server or open up the ports.

DMZ should work fine to the ATA.

I have had Vonage here and used the very 1st ATA they had, the old Cisco one, I now use LinkSys PAP boxes and they work just fine if the ports are opened up

[Cees]

ATAs are either SIP or IAX - 99% of them are SIP, SIP uses port 5060 by default and a range of 10000-25000 for the RTP protocal.  If both of these ranges are not open, you can make calls just fine, but receiving them will be hit/miss.  Either configure your ATA to use a STUN server or open up the ports.

DMZ should work fine to the ATA.

I have had Vonage here and used the very 1st ATA they had, the old Cisco one, I now use LinkSys PAP boxes and they work just fine if the ports are opened up

Your proposed setup does not work with the "production version" of the EU firmware for many people.  Vonage seems to work with your firmware however, which is strange.

I tested with all the ports you mention open and forwarded to my ata/phone, and also with DMZ to my phone and it does not work with "out of the box firmware 2.01EU".

Now I am using a beta-firmware which has also a version 2.01EU, but with a different issue-date (june 30, 2009) an SIP works normally.  (Even without portforwarding) So there is something wrong with the default firmware and not with our settings......