Yes, yes, yes…there have been issues with regard to restoration and licensing in the past. We had a lengthy conversation with @ncorbic about this a few months ago. The team has been working hard to rework the restoration vs licensing…we’ll just say “conflict”…in recent months.
This has been a matter of particular interest to us here at TheWebMachine Networks - we do dozens of migrations every single week - and we check back on it often. At last complete testing just a couple weeks ago, we didn’t encounter any issues with commercial module data restoring without the activation/licenses in place before the restore…but you still have to move the activation/license(s) in place after the restore, before you’ll be able to utilize the modules on the new system.
To say there is “no way to activate the commercial modules on the target” is misleading. As soon as you Zend Reset the Deployment ID from the old system to the new system after restoring the data, your commercial modules will be configured and working just fine. Even when there was an issue with restoring commercial module data on an unactivated system, you could still Zend Reset and move the Deployment ID and then restore all your data, commercial modules included, without issue.
Of course, as @lgaetz suggests, no one can even begin to fix any of these issues you might still be experiencing if you don’t report them in the bug tracker! Complain all you want, but we can’t fix it if we don’t know what’s broken.
There’s always a way…
- Compare the DB contents from both systems…while some core modules obviously change DB structures across versions, a lot of modules are rather major-version-agnostic in nature (you’ll note that the Bulk Handler version is still v13, even on v15 systems). An unactivated module won’t add to to the dialplan in /etc/asterisk/*.conf until it is activated, but the config will still be populated in the DB.
- In the case of EndPoint Manager, you can confirm that /tftpboot/ contents match up between systems and also confirm via its tables in the DB.
In short, Restore will populate the
asterisk DB tables for those commercial modules. Activation will expose/unlock the GUI pages AND allow the appropriate dialplan to be generated from the DB for those modules.