Migrating Elastix with FOP2

  1. 11 years ago

    Hi,
    I am replacing my elastix cluster and when I did a restore of the configuration from elastix it was not successful in having a working FOP2. I did a uninstall and then yum install and now have a version that works but is unlicensed. I can see all my configuration under buttons and such.

    I don't want to take down the production server to move the license.
    Do you have a trail key I can use to prove the backup and restore process I am implementing will work, or do you advice new key for migration?

    I also noticed the Elastix operator panel didn't migrate the extension configuration, I still had my one pre-restore test extension showing. It does update if I make a change to an extension. Not sure if EOP is using any part of your FOP to operate. Please comment if fixing my FOP2 install would help with this issue with EOP if you are aware of dependancy.

    Thanks

  2. admin

    28 Mar 2013 Administrator

    Hi,

    FOP2 is not related at all to EOP, so nothing you make in FOP2 will affect FOP2 and viceversa.

    Regarding the license, you can test your install using the lite version, but as you see it will only show you 15 buttons. You can revoke the license on the other server and register on this new one, and if you are unsatisfied with results you can revoke the new server and register again the other one. The command to revoke is /usr/local/fop2/fop2_server --revoke, and to register again /usr/local/fop2/fop2_server --register

    Best regards,

or Sign Up to reply!