Sangoma 7.6–1910 OR 2008 install
After successful install, log in to web and make sure everything is OK.
No need to sign in or create account, just click Abort.
Now, there is 2 main issues.
- The dependencies management of the module system. You can’t disable module without first disable all modules that depend on it. But you won’t know it until you try to disable it. If you try to disable more than one module in the same command and one of the modules return an error — all the following will be ignored.
- When you delete a default module — it will reinstall itself in the next update.
To deal with the second, we will only disable the modules, instead of delete.
To deal with the first, we disable each module in a seperate command, so in case of an error we can re run the command after disabling the dependable modules.
Now enough talking! Here is a simple command to disable all the enabled commercial modules:
fwconsole ma list | grep Enabled | grep Comm | awk '{print $2}' | xargs -I % sh -c 'fwconsole ma disable %'This will run fwconosle ma disable for each commercial enabled module. Probably some of the command will fail, but you can just run it again. In case the dependent modules are in the list (like zulu) the second time will succeed.
