Page History

...

1. Download and execute the register utility to generate a valid license.

   1. Download the register utility to the root home directory of your Asterisk server. First, log in as the user "root".

      No Format
      title Command-line Example for 32-bit Linux
      # cd /root # wget http://downloads.digium.com/pub/register/x86-32/register

   2. Change the permissions of the /root/register file to r-x------.

      No Format
      title Command-line Example
      # chmod 500 /root/register

   3. Run the register utility and follow the interactive instructions. The registration utility will prompt you for your DPMA license key.

      No Format
      title Command-line Example
      # /root/register

      Note
      title Internet Access
      Internet access is required from your Asterisk server in order to register your DPMA key for licensed use. Outgoing network traffic to TCP port 443 (SSL) must be allowed in order for the register utility to successfully communicate with Digium's license server and complete the registration process.

2. Download and install the DPMA binary that is built for your platform.

   Info

   There are versions for releases of Asterisk 17, 16, 15, Asterisk 14, Asterisk 13, and releases of Certified Asterisk. Take note that DPMA binaries are not loadable in prior releases of Asterisk, and will only load in the specific version for which they are designed. Be sure that you download the correct version of the DPMA binary for your Asterisk version. DPMA 2.3 is the last version for Asterisk 1.8-cert DPMA 1.7 is the last version for Asterisk 10 DPMA 3.4.3 is the last version for Asterisk 11 DPMA 2.3 is the last version for Asterisk 12 DPMA 3.4.8 is the last version for Asterisk 14 DPMA 3.5.1 is the last release for Asterisk 15

   Tip
   Updated builds of the DPMA binary are frequently released. Each build has a 'version number'. This version number is part of the filename, and is also included in the copyright/license message that is displayed when the module is loaded into Asterisk. In this document, build number '3.25.0' has been used as an example. Keep in mind that the build number may be newer when you read this document.

3. Download DPMA to the root home directory of your Asterisk server,

   No Format
   title Command-line Example for 32-bit Linux
   # cd /root # wget http://downloads.digium.com/pub/telephony/res_digium_phone/\ asterisk-13.0/x86-64/\ res_digium_phone-13.0_3.5.0-x86_64.tar.gz

4. Expand the res_digium_phone archive and copy the DPMA binary to the /usr/lib/asterisk/modules directory.

   No Format
   title Command-line Example for 32-bit Linux
   # tar xzvf res_digium_phone-13.0_3.5.0-x86_64.tar.gz # cp /root/res_digium_phone-13.0_3.5.0-x86_64/res_*.so /usr/\ lib/asterisk/modules

   For a RedHat or CentOS 64-bit distro (where a /usr/lib64 path exists), copy the modules to the /usr/lib64 directory instead:

5. No Format
   # tar xzvf res_digium_phone-13.0_3.5.0-x86_64.tar.gz # cp /root/res_digium_phone-13.0_3.5.0-x86_64/res_*.so /usr/\ lib64/asterisk/modules

6. If you already have a configuration file present from a previous installation, skip this step. Next, copy the res_digium_phone.conf.sample sample configuration file to the /etc/asterisk directory and rename it res_digium_phone.conf.

   No Format
   title Command-line Example for Config Copy
   # cp /root/res_digium_phone-13.0_3.5.0-x86_64/res_digium_phone.conf.sample \ /etc/asterisk/res_digium_phone.conf

7. The DPMA binary must now be loaded. (See General Notes to use multiple licenses on one server.)

   No Format
   title Command-line Example for new installs
   # asterisk -rx "module load res_digium_phone.so"

   No Format
   title Command-line Example for a DPMA upgrade
   # asterisk -rx "module reload res_digium_phone.so"

8. Verify that DPMA is licensed and operating. This can be verified by issuing "digium_phones license status" in the Asterisk CLI.

   No Format
   title Command-line Example
   # asterisk -rvvv *CLI> digium_phones license status OK, Valid product license found

9. Copy the generated license files to a safe place as described in the Backup Procedure section.

...