Print

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

[msinkm]

I was having some problems with version 3.01, which the router shipped with, so I thought I'd try upgrading the firmware to 3.10.  With 3.01, I could get a sipura SPA-2000 registered and working with a trixbox at another location, but with this version of the firmware, there was no way to make it work.  I could get the phone to register, and even to ring if and only if I enabled the SIP alg, but there was absolutely no RTP traffic allowed through with or without RTSP, SPI, or any of the other alg's enabled or disabled.

Finally, I had to take the router out and put in a different router I had on hand, and of course, I could get the VOIP working again.

I sincerely hope this problem will be dealt with soon.

[myknild_vp]

I bought a new router DLINK DIR-615. I connected my machines and VOIP phones directly to router. One of the VOIP phone was sip phone. Everything was working.

Then I forward my http port to one of my LAN machines. It did not work. I searched internet and found new firmware from D-LINK. I upgraded the firmware to 3.10 rev C.

Now my http port forwarding is working but sip phone had stopped working. I get a dial tone but could not place call. I get the incoming ring but it does not connect with caller.

I could not find a solution to this problem. I have switched back to my older router.

The only option left is to return the router.

[gerritv]

I will add my name to the list begging for a solution. I have an old router in the meantime but I really need the 615 to either get fixed or some way to roll back to 3.01.
There are similar sounding issues in the 655 section of this forum, common code?
Not a complex setup, cable modem->DIR-615->PAP2T with PBX In a Flash as the Voip server. This was working unitl I upgraded (or is it downgraded) to 3.10 to handle some WHS issues.

Please, pretty please........

[gerritv]

Good news. In spite of the statement that you can't go back to 3.01, in fact you can. You need to edit the .bin file (the 3.01 version) by inserting 3030 hex in front of the AP81 text string at the tail of the file. In the process you will increase the file size by 2 bytes. To be really clear, you will move the existing AP81... string over by 2 bytes, and the void created is filled with 2 ascii 0's (3030 hex).

I am sure this is not supported nor desired by DLink, however the alternative was spending a bunch of $ that I don't have right now :-)

[indecizo]

I'm in this list as well.  I wish I had read this post before buying.  Thanx to gerritv I was able to go back to 3.01 and i'm ok again.  But.... I'm sure this will come back and haunt me.

[dwpmr]

Add me to the list as well.  I upgraded from 3.01 because of frequent loss of connection at the suggestion of Dlink's "tech" support and immediatley lost my VOIP service.  Dlink denies any responsibilty for this issue, and won't authorize a refund.  I am finished with dlink - never again will I use one of their products.  My old Netgear router works like a champ.

[3cxman]

I will add my two coppers to this. I have a DIR655 and incoming SIP calls are not working.

The 655 is H/W A2 f/w 1.21  Linksys SPA921 phone connected to a port on the 655, It registers OK and handles outgoing calls OK.  Incoming calls is the problem for me.

Call scenario: Incoming internet call from a Askerisk or 3CX IP-PBX rings the phone. Called party answer the phone, Phone displays connected, but the calling party is still listening to ringing tone.

After wasting few hours,the only way I have managed to get this to work.

Enter the SIP phone into DMZ with QoS enabled.  It will not work if you don't enable QoS Interesting!!!!
I also found out, that entering ports 10,000 to 20,000 into port forwarding and DMZ off, you can then answer the call, but no voice transmission.

I have played around with SIP ALG feature, but it seems to do NOTHING. 

If the IP-PBX is on your LAN side of the 655 router, then you have no problems.  But, you will have issues with registration to a SIP network provider. The issue is, the IP-PBX VoIP truck will register when first configured and asks for service and all works well until you shut down the IP-PBX server, When you bring the server back into service, it can't re-register with your SIP provider and until you change the static IP address of the IP-PBX. Then, it will register with you provider.

I think both these issues are related.

These SIP issues, also applies to DIR615 router

[hubbard]

how exactly should the ap81 string appear after you've edited the bin file? It would be nice to have a captured image of that if possible?

Thanks so much.

This newer firmware is causing all sorts of problems for SIP. Other than somehow downgrading are there other options?

Hopefully I can figure out how to downgrade.. have a hex editor but am not sure exactly how it should look...

Thanks,

Hubbard

[gerritv]

Hi
You need to make the 301 file look like the 310 file. You do this with a tool such as WinHex. Note that you must move the string 2 Ascii (4 hex) digits to the right, then place 3030 hex into the spot you just opened up.
E.g. the string in the original 301 file looks like: 41 50 38 31 etc. You need to make it read 30 30 41 50 38 31 etc where the first 30 is in the position formerly occupied by 41.

[hubbard]

I think we're writing back and forth.. thanks for your help Gerrit...

In my version it goes 00 00 41....

Do those 00 00 stay or go?

Thanks,

Hubbard

[hubbard]

Never Mind.. I figured it out.. 00 00 stays obviously...

Cheers..

Hubbard

[Simakosmos]

Could u please send me edited file I can find full version of winhex and the trial one cant edit and save file larger than 200kb. Thanks - simakosmosizdalekogsvemira@hotmail.com

[Whistle]

Thanks for all the info! I will refund the router I just recently bought... I passed a few hours to wondering why my VOIP setup wasn't working. I have an older d-link and it works great

[XtcruleZ]

I have absolutely NO idea how to hex edit. Could someone that has done this successfully please email me the 3.01 bin file they have edited to work? I am having nothing but problems with the 3.11 firmware and i just want to go back to the way i had it before. kryp2nite26@gmail.com

[YGator]

I have an SPA3000 that has an FXS and FXO.  Ever since putting in this router it would sometimes work and most of the time not work.  I then went back to version 3.01 as suggested by gerritv.  However, the SPA3000 only worked for less then a day.  I had it setup as a virtual server for port 5061 (FXO) and one on port 5062 (FXS).  For RTSP I had Port Forwarding setup for port 10,000 - 20,000.  When this ended up failing I changed my setup to have all three sets of ports as Port Forwarding.  I did this change over a week ago and it has never stopped working.

Thanks to gerritv on figuring out how to load the old 3.01 firmware.