TIPS FreePBX Backup/Restore Fails to Restore OSS Endpoint Manager settings

[chris_c_]

Steps to reproduce.
1. install incredible 13 on ubuntu 14.04 32 bit, with incrediblefax and oss endpoint manager.
2. configure some endpoint (phone) brands, such as cisco/linksys, scan for mac addresses, save settings.
3. make backup with incrediblebackup.
4. make new vps server, centos 7 32 bit.
5. install incredible 13 centos.
6. Fix incredible 13 install script bugs until it installs correctly.
7. restore backup from step 3 into this new centos 7 32 bit incrediblepbx.
8. Go into Module Admin, install oss endpoint manager.
9. Go into OSS endpoint package manager, see big error message:

Cant find file: /var/www/html/admin/modules/_ep_phone_modules/endpoint/cisco/spa/family_data.json

10. Go into OSS Endpoint Advance Settings.
11. See old (totally wrong, will not work, private non-routable) IP address listed under "IP Address of Phone Server".

Q1: Shouldn't the incrediblerestore script do an automatic "Determine for me" to auto-set the new IP address of the phone server ?
Q2: Shouldn't the incrediblerestore script either
a) detect that OSS Endpoint Manager is missing and auto-install it so that settings can be restored properly into it? or
b) notify the user that OSS Endpoint Manager is not installed, then halt the restore to give you a chance to go and install it? or
c) restore the settings into a place which would not be clobbered by the subsequent installing of OSS Endpoint Manager?

 

[wardmundy]

Incredible Backup was built long before there was an OSS Endpoint Manager. Incredible Backup is an open source script. EPM is as well but it has required pieces that reside in a proprietary repository as best I can recall. If you can identify where EPM places all of its components, it's extremely easy to add that to the script and share it.

 

[chris_c_]

Incredible Backup was built long before there was an OSS Endpoint Manager. Incredible Backup is an open source script. EPM is as well but it has required pieces that reside in a proprietary repository as best I can recall. If you can identify where EPM places all of its components, it's extremely easy to add that to the script and share it.

I suspect that the OSS EPM is storing some of its state data in its module folder, not just in the database. It needs the files that it put in /var/www/html/admin/modules/_ep_phone_modules
Whenever you "install" a brand of phone to the list you want it to auto-recognize on your phone system, it creates data files in this folder tree containing data related to the phone models made by the manufacturer.
Can this folder, and all folders under it, be added to the list of folders to backup and restore - if it exists on the source system.

 

[ostridge]

Hi Ward, is there a good reason why we should not add /etc/iptables to that script? or would that b**** up something?

 

[chris_c_]

Further evidence....
On the same fresh system which is running the restored backup created with IncredibleBackup,
And you've manually installed the OSS EPM module using Module Admin,
When you go into the OSS EndPoint Manger, and try to add an extension, as you normally do, you get this error message:

Brand Directory 'cisco' Doesn't Exist! (/var/www/html/admin/modules/_ep_phone_modules//endpoint/cisco)
Invalid Model Selected, Can't Sync System!

 

[chris_c_]

I just verified that my suspicion was true.
While /var/www/html/admin/modules/_ep_phone_modules EXISTS on the source system, the same folder DOES NOT EXIST inside the tarball created by Incrediblebackup.
This folder should be added to Incrediblebackup's list of folders to backup, because the OSS EPM module is counting on the files it contains to be there, otherwise, you get all those errors as posted above, and OSS EPM fails...

 

[wardmundy]

Check the tar lines in incrediblebackup. At least in the ones that I have, the first entry is /var/www which would tell tar to grab everything in /var/www and below. If your version doesn't look like that, then let me know the details of running pbxstatus or status so we can check it.

 

[wardmundy]

Hi Ward, is there a good reason why we should not add /etc/iptables to that script? or would that b**** up something?

It's been a long time ago but I think the reason I didn't include the firewall setup is because of the likelihood that some folks were using incrediblebackup to clone a machine for use somewhere else. That would mean that differences in the whitelist might lock somebody out of their own server. It's easy enough to add. Just search for the tar lines in incrediblebackup and plug it in. Keep in mind that it's /etc/iptables on Ubuntu/Raspbian, /etc/sysconfig/iptables and /etc/sysconfig/ip6tables on RHEL/CentOS/SL, and /etc/network on some earlier RasPi platforms.

 

[krzykat]

I didn't include the firewall setup is because of the likelihood that some folks were using incrediblebackup to clone a machine for use somewhere else.

Yes - people use it for that exact reason I personally do copy my iptables across as its got myself whitelisted in there along with any special considerations I have.

Speaking of such, what will happen if I have a 32bit Centos 6.7, Asterisk 13.8 on Digital Ocean and I go to carry it over to Vult on 32bit Centos 6.8, Asterisk 13.10 - there should be no issues, right? Even if it went from a 32-bit to a 64-bit, I assume your worst case scenario would just be to recompile asterisk after the move? I don't remember, but I think that's what I did when moving from Wable to DO.

 

[chris_c_]

Check the tar lines in incrediblebackup. At least in the ones that I have, the first entry is /var/www which would tell tar to grab everything in /var/www and below. If your version doesn't look like that, then let me know the details of running pbxstatus or status so we can check it.

Mea culpa. I thought that IncredibleBackup had supplanted/overwritten the menu option, inside the web interface, "Admin / Backup and Restore", so I was just running the backup inside the web interface, which is the buggy one that omits the OSS EPM data files in /var/www/html/admin/modules/_ep_phone_modules. In fact they are two separate, yet overlapping, backup utilities. IncredibleBackup is a simple command line shell script which grabs a larger set of system data files, including the entire /var/www tree, which contains the endpoint phone modules files.

 

[wardmundy]

Mea culpa. I thought that IncredibleBackup had supplanted/overwritten the menu option, inside the web interface, "Admin / Backup and Restore", so I was just running the backup inside the web interface, which is the buggy one that omits the OSS EPM data files in /var/www/html/admin/modules/_ep_phone_modules. In fact they are two separate, yet overlapping, backup utilities. IncredibleBackup is a simple command line shell script which grabs a larger set of system data files, including the entire /var/www tree, which contains the endpoint phone modules files.

Oh, sorry. Yes, the one in the GUI is the creation of the FreePBX Dev Team IIRC.