D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-825 => Topic started by: Cees on August 09, 2009, 08:09:31 AM
-
I have a DIR-825 since a couple of days, Hardware version B1, firmware 2.01EU (date Fri, 12, Jun, 2009 = latest european firmware) Have portforwarding for ports 25, 80, 443, 143, 993 via virtual server to a local linux server (192.168.0.3)
My (SIP protocol) VOIP phone (192.168.0.100) does not work anymore since I use this router. It worked fine on my old WRT54G. The phone logs-in normally at the voip provider but when I make a call, it seems that the ports are not forwarded or are blocked by the firewall. I have tried to manually setup portforwarding and virtual server instead of portforwarding.
I have tried many things, from disabling QOS, SPI, end point filtering and more but it does not work. I have also programmed DMZ for my ip-phone, but it does not work. Nothing found in the logfiles about frame drops. (I have setup a syslog on my linux-server)
There seems to be a bug causing frames dropped, as my setup has always worked with my WRT54, and should work with DMZ set, but it does not. The same setup works fine on a DIR-655 of a friend.
Does anyone have a voip-phone with SIP protocol working on the DIR-825? I like to know if I am the only one ( ;) ) with this problem, or is there a firmware bug ?
-
I have the same problem, SIP will not work with this router :-[ , NAT, virtual server , tried for many hours, but it will not work?? The (Siemens S450IP) will connect to teh SIP servers, will autenticate, callsetup will go ok, but I cannot get an answer message (this is the C7 name, do not know the SIP equivalent), so for some reason no speech path is created?? Is there anyone who has an idea why, or better have a solution???
Without SIP this (otherwise good router) is only to be used as an accesspoint......
Another thing, putting back my old router (WRT150N, with only port 5060 forwarded), works perfect. So modem etc are not the problem...
-
There is definately an bug in the firmware.
I bougth this router a few months back, and could not make VoIP work. After a lot of testing and failing I posted a support request with D-Link. They realized that it was a problem with the firmware, and through the weeks they sent me two beta-versions of a new firmware. Neither one solved the issue, so I returned the router to the shop.
This was in early July.
I can only advice you to contact D-Link support, and find out if there ane any firmware update release soon. If not, I would go with a different router.
Good luck! :)
JernWilly
-
I am using Vonage behind my DIR-825 with firmware 2.02NA. Everything works fine for me...FYI
-
I am using Vonage behind my DIR-825 with firmware 2.02NA. Everything works fine for me...FYI
Did you earlier use firmware 2.01 ? And if so, did you have issues with SIP/VOIP too ?
-
I did use the previous firmware with Vonage. I had no issues....FYI
-
My vonage works fine. No setup was necessary. I don't know what SIP is, ...but my SIP is disabled on my router and my vonage VOIP still works.
-
I have Vonage and OOMA running without issues on verB. It also worked with my old ver A.
-
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...
-
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...
Same here, all seems to work normally when you dial, only the last stage where the speech-channel is setup, does not pass the dir-825.
Maybe Vonage and OOMA do not use SIP protocol with their blackbox ? I have tested with voipbuster and callvoip which are 2 separate voip providers using standard SIP protocol.
If this was a portforwarding issue, it should work normally when DMZ is activated. As it also does not work with DMZ, it must be a firewall blocking issue. Switching-off SPI and other firewall settings does not help.
-
Same here. PhonePower VOIP with Grandstream ATA doesn't work, even with ATA in DMZ under firmware 2.02.NA
-
Quote from Cees: Maybe Vonage and OOMA do not use SIP protocol with their blackbox ? I have tested with voipbuster and callvoip which are 2 separate voip providers using standard SIP protocol.
I'm not sure if this thought process will help you..... I use B1 2.02 NA because my router is american, ..and vonage is an american VoIP. Is the SIP VoIP a european thing?
-
I'm not sure if this thought process will help you..... I use B1 2.02 NA because my router is american, ..and vonage is an american VoIP. Is the SIP VoIP a european thing?
Vonage does not use SIP protocol and there are american voip providers that use SIP.
I have been using this router with my providers ( voipcheap, draytel to name but 2) who all use the SIP protocol with no issues at all. This is with a version B1 and firmware 2.00 EU.
HOWEVER I upgraded firmware to 2.01EU and all voip stopped working. No matter how I tried to set it up made no difference. The only thing I could do, for the time being, was re-flash back to firmware 2.00EU until I can find a solution.
-
I have been using this router with my providers ( voipcheap, draytel to name but 2) who all use the SIP protocol with no issues at all. This is with a version B1 and firmware 2.00 EU.
HOWEVER I upgraded firmware to 2.01EU and all voip stopped working. No matter how I tried to set it up made no difference. The only thing I could do, for the time being, was re-flash back to firmware 2.00EU until I can find a solution.
Thanks for this info, so Dlink has introduced a bug in the later firmware versions. My router was supplied with 2.01EU from factory so I never tested 2.00EU.
Did any of you contact Dlink support and got a reply on this issue ?
-
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.
-
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?
-
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.
-
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.
-
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
-
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.... :o
-
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
-
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
-
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?
-
Yes. When I bought mine back in June, it was delivered with 2.00EU.
VoIP didn't work.....
JernWilly
-
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.
-
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?
-
I have the A1 1.01 firmware. I use OOMA w/ no issues.
-
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.
-
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
-
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......
-
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%
-
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.
-
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.....
-
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.
-
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?
-
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
-
...
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
-
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.
-
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.
-
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!
-
I'm using a Trixbox PBX through my 825 with ZERO issues. DO NOT USE DMZ... bad news and not needed.
-
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.
-
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.
-
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!
-
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.
-
Well, it doesn't work. With or without RTP.
The 5060 port is correctly set up as a Virtual Server.
If you have the chance, let me know what hardware and firmware revision you have on your DIR-825. I have B1, 2.01EU.
Thanks!
-
My Firmware is 2.02 NA
-
An update on my DIR-825 B 2.02NA with my VOIP configuration.
Originally my ATA wouldn't connect at all. I have no idea why. The router crashed and when it came back up, its been working great ever since. The QoS has been awesome. I can totally flood the internet link with up and downlink traffic and VOIP sounds great, doesn't miss a beat. Not even any problems with jitter. Very impressive.
Now if I can only get my iPhone to stay connected.
-
Check out this link on a fix for SIP.
http://forums.dlink.com/index.php?topic=8958.0
-
Fain or this is FW for NA router and for EU is not function :(
how i upgrade FW EU 2.01 to NA 2.02B1 ???
-
Fain or this is FW for NA router and for EU is not function :(
how i upgrade FW EU 2.01 to NA 2.02B1 ???
PM sent ...
-
Beta fix for SIP issues...
http://forums.dlink.com/index.php?topic=8956.0 -> NA Version
http://forums.dlink.com/index.php?topic=9161.0 -> EU Version
-
Here is link for FW 2.01EU beta 16, HW B1. After flashing FW is VOIP working correctly with SIP ALG on. I haven't yet noticed any issues in this FW version.
D-Link DIR-825, FW 2.01EU beta 16, HW B1
http://www.ulozto.cz/3562313/dir825b1-fw201eub16beta01-0713140201-.zip
-
I just wanted to say thank you to those who reported the SIP problem and those at D-Link who were involved in the fix. I spent hours trying to resolve my DIR-825 SIP problems before I saw there was a firmware beta patch. After installing the patch my voip services (and so far everything else) are working perfectly.
/cheer
-
Ok I had the same problem and i was getting a bit upset becasue i just flushed over $100 down the drain. After playing around with the advanced server (kicked all my computers off the net), port forwarding (didn't do anything to help) and disabling the firewall i finally found a solution that works for me. I using VoIP.com service with a Grandstream Handytone 286 ATA. This product uses SIP for calls. Once i made the change and the system started working i had to laugh. I enabled the SPI, set my UDP Endpoint Filtering to Endpoint Independent, and enabled the SIP ALG. Did a reset on the GrandStream and now it is registered and working great. I have made a couple of test calls in and out and everthing sounds like a regular phone. The reason i had to laugh about it is that i had a DIR-628 in place before this. On the firewall settings i had to set just the opposite to make it work.
DIR-825
Hardware version: B1
Firmware version: 2.02NA
-
Ok I had the same problem and i was getting a bit upset becasue i just flushed over $100 down the drain. After playing around with the advanced server (kicked all my computers off the net), port forwarding (didn't do anything to help) and disabling the firewall i finally found a solution that works for me. I using VoIP.com service with a Grandstream Handytone 286 ATA. This product uses SIP for calls. Once i made the change and the system started working i had to laugh. I enabled the SPI, set my UDP Endpoint Filtering to Endpoint Independent, and enabled the SIP ALG. Did a reset on the GrandStream and now it is registered and working great. I have made a couple of test calls in and out and everthing sounds like a regular phone. The reason i had to laugh about it is that i had a DIR-628 in place before this. On the firewall settings i had to set just the opposite to make it work.
DIR-825
Hardware version: B1
Firmware version: 2.02NA
Thanks for the advice! I did so and my SnomM3 registers with my sip.voicemeup.com - I can receive calls no problem but I cannot call out, it just hangs and disconnects. Any idea why I would be able to take but not send?
-
Beta fix for SIP issues...
http://forums.dlink.com/index.php?topic=8956.0 -> NA Version
http://forums.dlink.com/index.php?topic=9161.0 -> EU Version
I get the following error when trying the link above:
An Error Has Occurred! The topic or board you are looking for appears to be either missing or off limits to you.
Does anyone else have this error? Can you access the patch? Do I have to figure out how to get higher privileges?
Regards delafield
-
The other link no longer exists. Use this link for the Beta 02 code. It should correct the VoIP troubles as well.
http://forums.dlink.com/index.php?topic=8957.0 (http://forums.dlink.com/index.php?topic=8957.0)
-
You have got to be kidding me. The fix says:
"By downloading the beta firmware file, you expressly agree that the use of the firmware i your own risk and discretion."
As far as I am concerned, the dir-825 is not even a router if it is not capable of forwarding packets for a fundamental protocol. For d-link to claim this thing is a router is at least false advertising - it is not capable of performing its advertised task. And d-link wants me to take the risk in patching the firmware to get it to work as advertised? Hello, FTC, you there? This is not a router. Keep your nose out of my sip packets and forward them like a router would.
I want my money back because of that disclaimer. Only after I do some more complaining elsewhere.
Once again. The dir-825 is NOT a router.
-
See my other post. Bottom line: not all VOIP hardware is compatible with type "N" wireless routers. Vonage and Talkswitch work with DIR-825 (most of the time), but Broadvoice does not. There appears to be a conflict with the type of protocol used and bandwidth. I also get some misdirection from the DIR-825. D-Link is aware of the problems according to Broadvoice tech support, but there does not seem to be any information when a fix is coming. Best advice, don't use the DIR-825 to route your VOIP traffic. I understand that Linksys type "G" routers work well with VOIP. Good luck.
-
^ I'm with you man, what a waste of money. I should get a refund not only for this unit but the amount of time I spent trying to get my SIP line working and the potential business calls I've missed. Last time I buy Dlink.
-
@TIAS. You said: "not al VOIP hardware is compatible with type 'N' wireless routers. Vonage and Talkswitch work with DIR-825 (most of the time), but Broadvoice does"
That makes no sense. I assume you misspoke, but i will clarify. We are talking about SIP, which is an APPLICATION layer protocol. It should not matter whether the router is a/b/g/n or even if it uses wireless at all. What you said is like saying "web browsing doesn't work on n routers." The router should be oblivious to the fact that the packet is sip. What dlink has done is try to add some sip application functionality to the router but they screwed up and are dropping sip packets - even when you instruct the router not to perform any sip application functions and act like a router should.
Regards
-
@tias - don't mean to take my frustration with dlink out on you, I just can't believe they are selling this thing in its current form.
Regards
-
I to have problems with voip. We use swyxit software at work. I first have to make a VPN connection and than connect trough the swyxit software. But no matter what I do can't get a connection with the swyxit software. The VPN works fine. Someone any idea. Router is dir825 b1 eu and firmware is the latest from the singapore server.
-
Hi,
The thread indicated below only contains a link to NA firmware. There is no EU link.
The other link no longer exists. Use this link for the Beta 02 code. It should correct the VoIP troubles as well.
http://forums.dlink.com/index.php?topic=8957.0 (http://forums.dlink.com/index.php?topic=8957.0)
-
Went out and got a Linksys WRT610 on sale, plugged it in and everything works out of the box. Fantastic. Sorry DLink but the 825 was just too much headache for me.
-
That's right.
I'm using a Siemens A580IP SIP phone. I did some packet sniffing between it and the 825 to try to see what was happening. Like others report with SIP ALG on I can register, but not make calls. And in fact I see my REGISTER go through and acknowledged, but SIP INVITEs do not get ack'ed. With the SIP ALG off I get no responses even from the REGISTER. This is very strange because in theory my SIP phone does not need any ALG support - all connections are made outgoing to the SIP server on the internet. It would seem the 825 blocks incoming (well I can't be sure if the outgoing packets are blocked) UDP packets even on a previously opened port, although I haven't experimented with other UDP applications.
I'll be trying 201EUbeta15 (now using 201EU), to see what happens.
@TIAS. You said: "not al VOIP hardware is compatible with type 'N' wireless routers. Vonage and Talkswitch work with DIR-825 (most of the time), but Broadvoice does"
That makes no sense. I assume you misspoke, but i will clarify. We are talking about SIP, which is an APPLICATION layer protocol. It should not matter whether the router is a/b/g/n or even if it uses wireless at all. What you said is like saying "web browsing doesn't work on n routers." The router should be oblivious to the fact that the packet is sip. What dlink has done is try to add some sip application functionality to the router but they screwed up and are dropping sip packets - even when you instruct the router not to perform any sip application functions and act like a router should.
Regards
-
I just received a new version of the firmware from tech support, 203NA and it solved all my VoIP problems. Downside, i had spent about 1 hour on the phone and went up to tier 3 to get it. Now at that tier, he knew exactly what the issue was and what needed to be done.
-
I just received a new version of the firmware from tech support, 203NA and it solved all my VoIP problems. Downside, i had spent about 1 hour on the phone and went up to tier 3 to get it. Now at that tier, he knew exactly what the issue was and what needed to be done.
I just called tech support and level 1 showed me the hand. Please post the firmware somewhere so we can fix our VOIP issues without draining an hour from each of our lives. I even told the rep that Level 3 had 203NA firmware that would solve my problem but got the "Sir, Unfortunately, the current release is 2.02NA. Check back on our website from time to time for updates."
Yeah, I'll wait 3 months to find it on your website someday. In the meantime, I'll pay my VOIP provider $$$$ and let this $175 SIP phone collect dust. >:(
My DIR-655 worked perfectly with the phone. The minute I "upgraded", no sound either way but the call will set up and the phone will register with my provider.
-
I have no idea about the protocol but I use Primus TalkBroadband up here in Canada behind my DIR-825 with no issues.
-
Well, after spending... yes, you guessed it- over an hour on the phone with tech support, I was told that there was no 203NA beta.
The good news is that the issue is resolved in the beta firmware here so you get to keep your hour:
ftp://ftp.dlink.com/Gateway/dir825_revB/Beta/Firmware/dir825_revB_fw_202b01NA_beta02.zip
I had downloaded this file and looked at the release notes prior to calling for support a second time but there is no mention of this beta release resolving the SIP ALG issues that everyone is experiencing. I can tell you that it does solve the problem. I was able to place the SIP phone in the DMZ or behind the firewall and get full functionality, voice and clarity both directions after applying this update.
I did not create any port mappings, virtual server settings or other VOIP/SIP related configuration. The only thing you need to do is be sure that SIP is checked (which they all are by default) in the Application Layer Gateway area (Advanced > Firewall Settings (bottom of the page))
Some notes:
- If you are using Tools > Admin > Administration settings, i.e. WAN-side remote administration, these settings will be defaulted off. You need to re-enable them after the update, including the graphical CAPTCHA login..
- Your wireless settings will be defaulted, too. You will need to re-configure both the 2.4GHz and 5.0GHz wireless radios. Be sure you know these settings before applying the update so you can re-create the configuration
- After the update, you will still see 2.02NA in the upper, right hand corner of the screen. Click on status at the top and verify that the build date is changed to 2.02NA , Wed, 7, Oct, 2009. This is your indication that the beta installation succeeded
You should have full VOIP access after this update. Please post any issues you encounter.
-
When are they releasing the newer firmwares? Are they releasing an EU version too?
I can honestly say, dealing with Dlink has been tedious, I don't think I'll buy from them again.
-
A new firmware has been released that addresses the SIP troubles.
http://forums.dlink.com/index.php?topic=12790.0 (http://forums.dlink.com/index.php?topic=12790.0)
-
Finaly VOIP is working !!
I have EU version, H/W B1 so firmwareupdate 2.03NA beta 02 is not working (I am unable to update).
I update my DIR-825 to 2.01EU beta 16 and now is VoIP working.
This firmware is different from 2.01EU because this was my default firmware na VoIP doesnt work.
Thanks to willly and his link: http://www.ulozto.cz/3562313/dir825b1-fw201eub16beta01-0713140201-.zip
-
A new firmware has been released that addresses the SIP troubles.
http://forums.dlink.com/index.php?topic=12790.0 (http://forums.dlink.com/index.php?topic=12790.0)
Yeah but where is the official EU version? Why only NA getting updated and not EU?
-
A new firmware has been released that addresses the SIP troubles.
http://forums.dlink.com/index.php?topic=12790.0 (http://forums.dlink.com/index.php?topic=12790.0)
Is there an EU release?
-
If you want to try the 2.03NA, this should allow it to load.
I have tried NA EU AND WW firmwares with this method.
Flush out the NVRAM Before you Re-Flash Your Router Updat
at
http://www.dslreports.com/forum/r22315498-Info-Flush-out-the-NVRAM-Before-you-ReFlash-Your-Router-Updat
Before and after you proceed.
now after the first time, at the end when you plug in but are still holding the paperclip to the reset:
when you remove paperclip you browse to 192.168.0.1,
You should see a loader that is unfamiliar, use it to browse to the bin you wish to load to.
Of course, you wish to have the bin file set in a location on your hard disk before proceeding.
-
Unfortunatly, the problem I had with my linksys spa2102 is still present in firmware 2.03NA. Back to firmware 2.02NA beta 2 and my voip works once again. (using rev b of the router).
-
Dear all!
Let me describe my experience so far with the DIR-825 and VOIP. I am using a Siemens Gigaset C475IP using the SIP protocol using two SIP providers (one of them sipgate.de).
The C475IP was working fine with my old router from siemens using port forwarding for the ports 5000-5070 TCP and UDP (the whole range for convenience ;) ).
Now with the new D-Link router with firmware 2.01EU which was shipped with my DIR-825. Nothing (!) worked, although I was using the same port forwarding settings.
After updating to firmware 2.02EU Voip was working perfectly for outgoing calls but was not working for incoming calls. (Which I only found out when somebody called me after a couple of days and he could hear me but I was not hearing him.)
I was trying several things: virtual server just for the needed ports, port forwarding for the range as explained above, and also SIP Application settings on and off. Nothing (!) fixed the problem. >:(
The only thing which was left was putting the VOIP phone C475IP in the DMZ. That worked. But of course this solution is only a second best solution and has potential security issues.
To make it short: There is clearly still a SIP bug in the 2.02EU firmware and I am about to give back this buggy router or resell it.
Regards
Wikilover!
-
I hope D-Link engineers read these forums, as this is a bug with their DIR-825 firmware. Most likely with the SIP ALG.
No matter what I do to the port forwarding or virtual server (or DMZ). no matter what I try (spent an hour on phone with dlink tech support), UDP port 5060 is "locked" by the firewall, and i cant successfully get 5060 UDP to open. I am using PFPortChecker ver 1.0.32 by portforward.com (free UDP port scanner). i can open TCP 5060 or any other port both UDP or TCP and PFPortChecker is successfully able to scan the ports as open, but not UDP 5060.
I WOULD BET DLINK ENGINEER $100 or a case of thier favorite beer that IT IS A BUG!!!
We are a national Hosted UC provider serving ~10,000 seats. We use Nortel MCS5200 (carrier grade SIP (VoIP) multimedia switch), along with Nortel PC Client (softphone you install on your PC) to make and receive calls, click to call, IM, co-web browse, presence, etc.
-
I have to be able to use the Nortel PC Client when working from home. The WNDR3700 was $5 less than the DIR-825, and my VoIP worked instantly after I unchecked the SIP ALG box! I didn't read great things about the Linksys E3000 either. What would you suggest? I need the sim dual band to connect to a 5Ghz bridge to stream media to TV's, 2.4Ghz is for pcs and laptops.
-
I'm on a DIR-825 Rev B. The router shipped with firmware 2.02NA, which I could not get the SIP phones to work through. I updated to the latest firmware, 2.03NA, tried disabling SPI, enabling/disabling ALG, and still no dice. This router has serious issues with SIP phones, and unless D-Link does something about the bugs, it will not work. We replaced the DIR-825 with a WRT54GS2, which worked right out of the box.
-
The problem with SIP on the DIR-825 A & B is that the SIP ALG firewall does not take into account port 5060 used my many VoIP service providers. To fix this, check the logs for outbound ports that are being blocked by the SIP ALG firewall. Go to Advanced, Application rules and add a rule, ie Voip for UDP port 5060, trigger and firewall, this will stop the port 5060 outbound blocked messages in the log.
Next assign the Voip TA a DHCP IP reservation under Setup, Network Settings then add the now static DHCP IP address to Advanced, QOS rules and only give that IP address, ie 192.168.0.199 thru 192.168.0.199 a Priority of 1, "Any" Protocol, ports 0 thru 65535. I recommend changing the VoIP TA IP address to 192.168.0.100, leaving the DHCP leased / expires in the 170 to 190 range. ie, what IP you assign on the router the TA will pick up based on mac address. Leave the Remote IP Range 0.0.0.0 thru 255.255.255.255. You must place the VoIP TA in the DHCP reservation list because the QOS Rules will not follow a DHCP IP lease expiration if your TA is assigned a new IP address by the router.
Limited to a number of SIP applications this router recognizes automatically, ie Skype, AIM Talk, Calista, ICQ, Pal Talk - all PC based applications, D-Link engineers did not take into account firewall settings for physical TA's like Vonage, ITPVoIP, and others. Your VoIP TA and service provider may be slightly different, but you get the idea how to use Status, Logs and Advanced, Application rules to open blocked outbound ports and use QOS firewall settings to prioritize VoIP traffic. If you follow this setup you will also eliminate the "Blocked outgoing ICMP packet (ICMP type 3)" message in logs.
-
Problem SOLVED
Outgoing calls were working fine, but incoming calls did not get through.
In "ADVANCED" > "FIREWALL SETTINGS", I unchecked "Enable SPI". Rebooted.
Works fine.
Max
-
Unfortunately turning off the routers firewall which is your front line defense against internet attacks is not a brilliant idea nor does it solve the problem of VoIP network packet prioritizing which you will run into when gaming or uploading / downloading large files while on the phone simultaneously.
Well... Unless voice chop, missed and disconnected calls is acceptable during these events.
-
Ok I had the same problem and i was getting a bit upset becasue i just flushed over $100 down the drain. After playing around with the advanced server (kicked all my computers off the net), port forwarding (didn't do anything to help) and disabling the firewall i finally found a solution that works for me. I using VoIP.com service with a Grandstream Handytone 286 ATA. This product uses SIP for calls. Once i made the change and the system started working i had to laugh. I enabled the SPI, set my UDP Endpoint Filtering to Endpoint Independent, and enabled the SIP ALG. Did a reset on the GrandStream and now it is registered and working great. I have made a couple of test calls in and out and everthing sounds like a regular phone. The reason i had to laugh about it is that i had a DIR-628 in place before this. On the firewall settings i had to set just the opposite to make it work.
DIR-825
Hardware version: B1
Firmware version: 2.02NA
I used this solution with my DIR 825 HW Version B1 Firmware 2.03NA with Fonality SIP VOIP phone (Grandstream GXP2000) I had spent 90 minutes on the phone with Fonality before they said "you need to go back to the DIR 655". After deploying the above solution, the phone worked until the next morning. Then I made one change, disabled the SPI and got it working again. Time will tell though if this is a lasting solution.
-
would adding a switch get around it to the 825
-
It's possible there are other issues when using VOIP. Seen issues lie with VOIP HW and SW rather than DLink routers.
Also placement of the VoIP devices reserved IP address in the routers DMZ resolves this problem.