Still having trouble updating to FreePBX17

FreePBX Installation / Upgrade
1

I am currently running FreePBX 16. I want to upgrade to 17. I started by running a full backup. I followed the instructions here to get ready for my new install on a virtual machine.

Problem 1: Step 28 (apt-get -y install net-tools htop screen tshark vim sngrep) failed because it was looking for local media, but this showed me how to fix it.

Then I moved on to installing FreePBX following the instructions here.

Install ran fine, so I restored from my backup.

Problem 2: Then I went to activate the system, and got stuck in an endless activation loop, redirecting to port 8080 over and over. I followed the instructions here to get out of the loop, which worked after I found the missing semi-colon at the end. Then, magically, the system was already activated.

Finally, I got a new Let’s Encrypt certificate for my DDNS, and got it installed.

Problem 3: Most phones (a variety of old Polycoms and half a dozen Digium D60’s) registered with the new server right away, but two Digium D70’s failed to ever even contact the new server, no matter what I did.

Problem 4: In attempting to debug problem 3 I looked at the log, and it was going crazy. The main thing that made me think I had a real problem was errors like this for a variety of extensions that were registered and seemed to be working properly:

PJSIP MESSAGE - Could not find endpoint [ip address of an extension here] and no default outbound endpoint configured

I also noticed that one of the daemons wasn’t running. So I attempted a restart to see if that would fix anything. Instead, now two daemons failed to start.

So I gave up and shut the new virtual machine down and fired up the old one for now.

Any advice for me? Did I do things out of order? Something else I did wrong?

Thanks in advance!

2

If you don’t have a lot of extensions, just recreate the config from scratch instead of restoring a backup. I’ve done that, and it saves a ton of headaches later, plus it forces me to remove and cleanup old/unused things.

Then, if you still have issues after the from-scratch config, let us know what is still not working.

3

That’s a lot of work. About 50 extensions, some with users and VM, special settings for multicast for some of the phones, etc.

I can do it, obviously, but boy do I want to avoid it if possible.

Edit: I don’t even know how to bring over the users’ VM PINS and custom VM greetings. I wouldn’t be surprised if I ran into other things I didn’t know how to bring over.

4

There is no need to reconfigure from scratch if you want to avoid having to reconfigure a bunch of extensions, DIDs, Trunks etc. I had a couple issues where Backup/Restore didn’t do something quite right. I don’t remember off the top of my head what the issues were but they were related to extensions. I just used the bulk handler module afterwards to correct that.

Using the bulk handler is fairly self explanatory. Just export whatever things you need to the spreadsheet, compare that exported spreadsheet to an example spreadsheet on the new server, make the necessary changes, and then import it.

1 Like
5

Thanks. Somehow I forgot about using a spreadsheet, even though I created most of these extensions the first time using a spreadsheet.

I will probably try this.

I’ll first search to see if it is possible to manually move over old VMs and VM greetings and PINs.

If anybody would like to debug the issue in the logs, I’ve saved the VM.

6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.