/
Copy protection activation failing for licenses

Copy protection activation failing for licenses

This problem can be caused if the license (.lic) files are not found in the paths that Asterisk looks in, or if your system had a previous 32-bit installation of Asterisk that was not cleared and you installed a 64-bit version.

  1. Normally the license files should be set by default so that Asterisk looks in /var/lib/asterisk/licenses for the .lic files, so this would be the first thing to check.

  2. If the licenses are where they should be, the next thing to check is that Asterisk is being told to look in the correct directory. In the /etc/asterisk/asterisk.conf file there is a section that looks something like this:

[directories](!) ; remove the (!) to enable this
astetcdir => /etc/asterisk
astmoddir => /usr/lib/asterisk/modules
astvarlibdir => /var/lib/asterisk
astdbdir => /var/lib/asterisk
astkeydir => /var/lib/asterisk
astdatadir => /var/lib/asterisk
astagidir => /var/lib/asterisk/agi-bin
astspooldir => /var/spool/asterisk
astrundir => /var/run/asterisk
astlogdir => /var/log/asterisk

  1. If the 'astvarlibdir' is set to something other than /var/lib/asterisk, then either that path will need to be changed, or the .lic files will need to be moved to that directory. Or as an alternative, a symlink can be created to link the directories so the file does not have to be moved.

  2. If you have remnants of a previous 32-bit installation present, and have installed a 64-bit version, you will need to edit the 'asterisk.conf' file to change the 'astvarlibdir' value to point to '/var/lib64/asterisk'.

  3. Some repositories may contain versions of Asterisk that have this configuration altered from the default, so if downloading and installing the package from one of those repositories, this is something that should be checked.

  4. If the above steps have not helped, or if everything is already configured correctly and the .lic files are in the right place, it could be the permissions for those files. Check the permissions by running the command 'ls -l' on the Linux shell in the folder where those files are, and take note of the list that is displayed. You should see something like this:

--w-r--r-- 1 root root 0 2010-04-21 15:22 G729-1234567890.lic
--w-r--r-- 1 root root 0 2010-04-20 11:47 S4A-1234567890.lic

  1. The user permissions (underlined here: --w-r--r--) should at least be set to "read" (r--). In the list above they're set to "write" only. If they aren't set with the "read" permission level, run the command 'chmod 644 <filename>' for the license files. They should then look like this:

-rw-r--r-- 1 root root 0 2010-04-21 15:22 G729-1234567890.lic
-rw-r--r-- 1 root root 0 2010-04-20 11:47 S4A-1234567890.lic

Once this has been done Asterisk should be able to read the license files when the modules are loaded again.

Related content

Open Source - How do I correct the error "Command 'module load codec_g729a.so' failed"?
Open Source - How do I correct the error "Command 'module load codec_g729a.so' failed"?
More like this
Open Source - How do I remove G729 license files from my server?
Open Source - How do I remove G729 license files from my server?
More like this
Open Source - How to correct Asterisk Ending With Exit Status 1
Open Source - How to correct Asterisk Ending With Exit Status 1
More like this
Changing Major Asterisk Versions on the Fly
Changing Major Asterisk Versions on the Fly
More like this
Open Source - G.729 Software Codec Does Not Load
Open Source - G.729 Software Codec Does Not Load
More like this
Open Source - Introduction to Digium Asterisk Module Licensing
Open Source - Introduction to Digium Asterisk Module Licensing
More like this
Unable to render {include} The included page could not be found.