Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_asterisk-fop2-upgrade [2014/10/24 23:43] – [Upgrade FOP2 via CLI] abelbeck
+++ userdoc:tt_asterisk-fop2-upgrade [2022/03/02 09:31] (current) – [Fixing Invalid FOP2 License] mkeuter
@@ Line 6: / Line 6: @@
 [[http://www.fop2.com/buy.php|License Upgrade]].
-If you have a FOP2 license, follow the steps outlined below to make sure FOP2 sees this as an "upgrade" and not a "new install".
+If you have a FOP2 license, follow the steps outlined below to make sure FOP2 sees this as an "upgrade" and not a "new install". The FOP2 license seems to be verified against the MAC-address of the first NIC __and__ your hostname. So be careful on VMs (MAC) or changing your hostname!
 !!Note: AstLinux 1.2.1 or later is required!!
@@ Line 44: / Line 44: @@
   service fop2 test
+If you'll get the error "Could not contact registration server, please try again later.", try this option ([[http://www.fop2.com/docs/faq.php#FOP2segfaultswhenItrytoregistermylicense|from FAQ]]):
+  /usr/local/fop2/fop2_server --upgrade --rp=http
+Sometimes the "service fop2 test" command will show you that you need to "reactivate" your license...
+  /usr/local/fop2/fop2_server --reactivate
 Finally, start FOP2 with the newly updated version...
@@ Line 51: / Line 59: @@
 !!Tip ->!! Should there be a problem with the new FOP2 version you may revert to the previous FOP2 version with "''upgrade-package fop2 revert''".
-!!Tip ->!! If you made customizations to the FOP2 files, those file are saved in the ""''/stat/var/packages/fop2-OLD/''" directory.
+!!Tip ->!! If you made customizations to the FOP2 files, those file are saved in the "''/stat/var/packages/fop2-OLD/''" directory tree.
 ===== Upgrade FOP2 via Web Interface =====
@@ Line 62: / Line 69: @@
 ===== Fixing Invalid FOP2 License =====
-An invalid license could be caused by a few reasons, if all else fails contact FOP2 support.
+An invalid license could be caused by a few reasons, if all else fails contact FOP2 support (and be sure to remember exactly the output of the ''service fop2 test'' command).
 First, using your original "serial code" you purchased, try to register...
   /usr/local/fop2/fop2_server --register
+If you'll get the error "Could not contact registration server, please try again later.", try this option ([[http://www.fop2.com/docs/faq.php#FOP2segfaultswhenItrytoregistermylicense|from FAQ]]):
+  /usr/local/fop2/fop2_server --register --rp=http
 If that fails, try to revoke your current license and then re-register...
@@ Line 74: / Line 85: @@
 If that fails, contact the fine folks at: [[http://www.fop2.com/|FOP2]]
+===== Re-Imaging with a FOP2 License =====
+If you have an installation with a license and want to rebuild or move the install to a different drive, a little planning with the following steps will make managing your FOP2 license easier.
+Before you rebuild the install...
+  service fop2 stop
+  /usr/local/fop2/fop2_server --revoke
+It then asks for the original registration code, hopefully "succeeded".
+Re-Image your drive, install a fresh FOP2 package via the System tab, then via the CLI...
+  service fop2 test
+  /usr/local/fop2/fop2_server --register
+It will again ask for the original registration code, hopefully "succeeded".