Print

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

[doug2]

I'm not sure if there is a correlation or not, but over the last month or two since I upgraded to 1.02.04e, several times the base unit has not been able to contact one or both of my 2 gateways.  I do know that in the couple of months I had the system before the firmware upgrade, this never happened, but the timeframe is too short to be certain that the upgrade and this behavior necessarily have anything to do with each other.

I'm guessing that, on the occasion I lost both, it was due to one having been lost, me not noticing (but still having outside lines - 3 on each gateway) and then the other one going out some time later.

I am also not sure whether they are rebooting, then failing to reconnect, or otherwise locking up.  I do know, however, that the *only* way I've been able to get the base unit to recognize them again (with multiple attempts and variations at power-cycling and/or pressing the reset button failing) is to remove them from the base unit in Administrator, reboot them, and add them again.

So this may or may not be the same as the reboot problem seen in a couple other threads (this has only happened a few times, not multiple times daily), so I wanted to differentiate it with a new thread.

[doug2]

So, I called the 800 number and discovered that there was an update to the base unit (was 1.0x.xxxxxx.06.04) to .06.05.  Had looked at the downloads page for the DVX-2000 before, but thought the firmware upgrade was actually the "original release" firmware.  Putting a firmware version number next to the download button (like all the downloads for the gateway and both phones) would be helpful.

We'll see if this solves it, or at least, if it is the gateways rebooting, perhaps the base unit will now reassociate with them after they do.

[dsiegel]

I have had this same issue with a similar setup and have been working with Dlink support to get it resolved. 

I have 2 DVG's with two lines in one and 3 in the other.  The users started to complain about dropped calls and eventually I was able to determine that the DVGs were rebooting several times throughout the day for no apparent reason.

Today is acutally the first day that they have not restarted.  I notice that my base unit is 6.04, I'm not sure if that has anything to do with it but below are the steps I have followed:

- put both units on a dedicated battery backup
- restarted both to factory default (FW:1.02.04e) and readded them to the system
- assign static IP and DNS addresses  ( reserved addys in DHCP server)
- attached lines in hunt group order

That last step was the last thing I did yesterday.  I actaully had them in reverse order becuase that is how most phone systems are setup, but the guy at Dlink said they should be attached in hunt group order and it looks like that may have solved the issue as both have been up for more than 21 hours as of right now.  (I hope I am not speaking too soon!)

[doug2]

Apparently one of the things that the .06.05 firmware fixes is some kind of memory leak.  Don't know how bad it is, but for that reason alone upgrading is probably not a bad thing...

[dsiegel]

I did go ahead and get the upgrade in over the weekend.  I'm not sure why that one had to be via USB, unfortunately it required a trip in to the office while all the other updates for VC have been through the admin software.

I did wind up turning up the volume on the lines a little from what I had posted before.   What I was using was low enought to take care of the static and hiss but apparently the audio was dropping out on occasion.

I am really interested in knowing what else everyone is doing to make this system work.  I will take the time later tonight to post a list of equiptment and settings, I hope we can exchange some good ideas.

[doug2]

Well, since I upgraded the base unit, have had no disconnects from the gateways.

As far as the USB upgrade goes, it may be that the RP spec/API for external network access to the device does not allow traffic other than VoIP and admin/assistant login and communication with the base station.  Either due to oversight, or for the purpose of physical security.

Again, I would STRONGLY URGE the D-Link website to put the VERSION NUMBER of the base unit firmware next to the download button on the support/downloads page.  Currently, it is *not clear*.