there’s going to be an uptick in our agency’s use of VoIP and I wanted to 1) upgrade our freepbx installs to the latest, and 2) move away from chan_sip to chan_pjsip before installing a bunch of new extensions. I did a test install and restore from the pbx being retired to a testbed vm and it all worked beautifully. Chan_sip trunks and extensions all converted and everything looked good. I did some more experimental stuff on that VM, with the idea that I would simply do the install again from scratch when it came time to implement. I also had some reasonably successful install, restore, deploy scenarios with 2 other PBXs elsewhere in our network, so I was pretty confident.
Going from the instructions on the wiki, I reformated my testbed VM, installed oldstable Debian and ran
(pretty certain that was what I did earlier when testing)
then I made a fresh backup from my current live PBX and restored to the testbed.
Early during the restore it threw the following error
Invalid sequence order: 2 on line 135 of file /var/www/html/admin/modules/core/Components/Outboundrouting.php
At the end of the restore things did not happen.
the chan_sip connections were not converted automatically as they had been every other time. hoping for the best, I ran the conversion command line, which reported converting all the connections but that made no difference to the gui. (see next)
the extensions and trunks are not showing up in the gui, even though I can find them in the mysql tables and the /etc/asterisk/ output files.
Interesting. I have the same exact same problem / error message, but all of my extensions are already pjsip. I just run the backup (multiple times with various options), run the restore, and I always get that error and a partial/minimal restore. Perhaps I have some FreePBX 16 setting? or do I have to rebuild my target pbx?
I spent some time looking through the backup file and I couldn’t find anything related to that file.
Nice to know I’m not going completely mad. It’s beyond my willingness and possibly ability to find out what is screwing up in the restore script now that wasn’t 2 months ago.
I assumed it was the chan_sip extensions but I have no way of knowing that. The only thing that made this fix possible was that my new pbx was a virtual machine that I could keep rolling back and forward to different states till I found something that worked.
Error Output:
ERROR at line 1: Unknown command ‘-’.
on line 235 of file /var/www/html/admin/libraries/Composer/vendor/symfony/process/Process.php
There were warnings during the restore process
Can’t find the module data for callback
Can’t find the module data for setcid
npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info.
npm WARN deprecated [email protected]: This version of ‘is-buffer’ is out-of-date. You must update to v1.1.6 or newer
So I installed SNG 7 / FPBX 16, asterisk-version-switch to v20LTS, then ran the restore. I got that error… which is different, but still deosn’t really get me anywhere, and honestly this looks like some kind of compatibility issue with the older software versions, so if I could get around it I’d be skipping part of the restore? I don’t know, maybe.
This appears to be an ‘import’ bug. I ran a backup of only the core module on version 17.0.18.44. I restored to the same version on a test machine, with the failure to import as indicated in the OP’s post. To resolve, and I’m sure there are other ways of resolving, I did:
fwconsole ma downloadinstall core --tag=17.0.18.40
… on the target machine. Then I used the same backup that errored to restore the core module, and it went through fine. I can see there’s a history of changes to the outbound route import settings in the changelog for the core module, so I assumed there was some kind of bug introduced to the backup & restore module that was unaccounted for.