I have this problem with the Dlink DVX-8000 IPPBX
-
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
This is the Elastix model of Asterisk. Nothing wrong with it, but when one of the underlying pieces fails, there is no obvious method of access or recovery.
Makes sense. So this is a long dead product. Probably no way back then.
-
@wersiy Do you have console access to this unit (command line?)
-
Please do you have any idear what i can do to at least bring the freepbx back up and running?
I will be very gratefull
support center haven't respond till now -
yes
even PuTTy -
@scottalanmiller said in I have this problem with the Dlink DVX-8000 IPPBX:
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
This is the Elastix model of Asterisk. Nothing wrong with it, but when one of the underlying pieces fails, there is no obvious method of access or recovery.
Makes sense. So this is a long dead product. Probably no way back then.
No, that is not what I said. Elastix is dead, but this is not Elastix.
I said this is the Elastix model. Meaning that they used the same Asterisk + FreePBX GUI + Customized. There is nothing wrong with this model, as long as the vendor will be there to support it.
-
for two days
-
@wersiy in all seriousness, if this was me, the first thing I'd be doing now is replacing this unit. There's no reason to have it, it's a dead product without support (the vendor that D-Link gets this from went out of business some time ago, and the product that is used from them has been out of support for many years even while the vendor was still around, it was an abandoned product from a now vanished company.) Even when it was under support and still alive, an appliance of this product made no sense and was a bad idea.
Even before this died, it really should have been replaced. A replacement would be free, modern, and supported. The D-Link hardware is just adding risk without benefit.
This might be a huge pain, I don't know how many users you have, but even a thousand users is only so bad to migrate manually. A pain to be sure, but only so bad. Moving to something like true FreePBX (the distro, not the GUI) is your best answer. Works basically the same and is basically 6-8 generations newer of essentially the production version of the thing that you have on that D-Link.
Do you have any server(s) in your environment?
-
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
@scottalanmiller said in I have this problem with the Dlink DVX-8000 IPPBX:
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
This is the Elastix model of Asterisk. Nothing wrong with it, but when one of the underlying pieces fails, there is no obvious method of access or recovery.
Makes sense. So this is a long dead product. Probably no way back then.
No, that is not what I said. Elastix is dead, but this is not Elastix.
I said this is the Elastix model. Meaning that they used the same Asterisk + FreePBX GUI + Customized. There is nothing wrong with this model, as long as the vendor will be there to support it.
OH, I thought you meant it was the Elastix model from D-Link. I get it now.
-
@wersiy said in I have this problem with the Dlink DVX-8000 IPPBX:
for two days
Ouch. D-Link has never been a real business brand. I'd avoid them in a business in the future as one of many port mortem take aways from this. But that doesn't help much now, but a little. We can fix that, literally, immediately.
-
The user manual says to click on unembedded FreePBX link. but You don't have the left menu to even see that.
So you are pretty much screwed.
You can spin up a new FreePBX instance on a VM faster than you can get support.
How many extensions you have?
What is your connection to the outside world? A SIP trunk or legacy?
-
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
You can spin up a new FreePBX instance on a VM faster than you can get support.
That's what I was saying too. This is the case here (and is the case more often than people realize) that a full fix is often faster than applying a band-aid.
-
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
What is your connection to the outside world? A SIP trunk or legacy?
He's on legacy lines, but with a SIP gateway. So to the PBX, it's all modern SIP. But limited to on premises.
-
@JaredBusch said in I have this problem with the Dlink DVX-8000 IPPBX:
How many extensions you have?
Two hundred.
-
@wersiy said in I have this problem with the Dlink DVX-8000 IPPBX:
for two days
A 2 day outage and no one has responded to you. . . Yeah time to fire them and not consider D-Link ever again. What @JaredBusch and @scottalanmiller are recommending are solid options.
Though @JaredBusch and @scottalanmiller how quickly could he get his numbers moved?
-
@DustinB3403 said in I have this problem with the Dlink DVX-8000 IPPBX:
@wersiy said in I have this problem with the Dlink DVX-8000 IPPBX:
for two days
A 2 day outage and no one has responded to you. . .
Not exactly an outage, but still ridiculous. D-Link is definitely not someone you'd want in a business. I remember when they were at SpiceWorld trying to convince people that they weren't just toy equipment for low end home deployments... but no one believed them. They kept claiming that they would send out free business gear for people to see, but they never managed to. I think their business division collapsed before it got started most likely.
-
@DustinB3403 said in I have this problem with the Dlink DVX-8000 IPPBX:
Though @JaredBusch and @scottalanmiller how quickly could he get his numbers moved?
As fast as someone can type them in
-
@JaredBusch
i've got over 200 extensions and two SIP trunks which connect through both GSM gateway and FXO gateway
all in house -
@DustinB3403 Probably quicker than waiting for D-Link to respond lol
-
@jmoore said in I have this problem with the Dlink DVX-8000 IPPBX:
@DustinB3403 Probably quicker than waiting for D-Link to respond lol
Quicker than fixing the box himself, too.
-
I agree that moving to a new system right away seems like the best course of action given that the phones are not actually down, but just cannot continue to be configured.
