As of this week, I have tried to provision digium phones, but they are timing out when trying to get to the asterisk server.
As a band-aid fix, I have used the webUI of the phones to register them through freepbx. This is of course not perfect, as a bunch of features such as RDK/etc are not able to be applied through the web interface.
Has there been any changes in the last week or two that cause my phones to no longer be able to contact Asterisk?
A note on network topology: For testing, the phones in question are on the same subnet/in the same building as the server, with no firewall or other network stuff in between them besides my switch.
I would not recommend a restore from AsteriskNOW to freePBX-15. Simply go back to the last VM version which worked, open the web-ui. Then install freePBX-15 to a new VM (with a different IP), open the web-ui. Now copy and paste manually every entry, which applies…and adjust the settings in the new distro.
I understand…
You could also go back to your last working version (Virtualbox VM) and then try to manually update the DPMA module.
Check my last post in this thread. There is a link to a special DPMA-version for Asterisk 11 (if you have this version). I don’t know if it works, but you could try. You could always go back…that’s the beauty of Virtualbox
The restore in FreePBX 15 is designed to allow a legacy restore from FreePBX version 2.9 and up. It really shouldn’t matter what distro you are running.
Legacy restore It generally works, BUT there are an enormous number of module combinations and versions, so it does happen that a restore is incomplete or fails completely. If you spin up a 15 system in a temp location and restore the tarball, it will give you an idea of what to expect.
That is what I am currently doing. I have backed up everything from my freepbx 12 system. I have yet to actually do the restore just in case it tries to use the same IP from the original config.
So I will be clicking the restore button after hours.