分类： LINUX
2009-01-06 15:13:40
So, you've received a free key for G.729. Congratulations, and thanks for stopping by the booth! Your instructions to install G.729 are as follows:
If you have followed all of the instructions in the README file and are unsuccessful or have other installation issues, please contact Digium support via e-mail: support@digium.com
Usage of G.729 with Asterisk requires two components, the codec binary and the register utility.
There, you will find the following subdirectories:
Inside the Asterisk version-specific directories, you will find sub-directories for processor types, such as x86-32 and x86-64. Users of 32-bit processors and distributions should choose x86-32. Users of 64-bit processors AND 64-bit distributions should choose x86-64.
Further, inside those directories are zip files containing codec binaries optimized for individual processor types. Contained in the name of each zip file is a versioning string, noted as, for example, v32. This notes Digium's release version of the codec binary.
The following are shown as an example of the x86-32 available builds:
The following are shown as an example of the x86-64 available builds:
Download the codec binary appropriate to your processor type and Asterisk version, unzip its contents (which contain a copy of the LICENSE file), and place the codec_g729a.so binary in the following directory on your system:
/usr/lib/asterisk/modules/
The second component required is Digium's register utility. The register utility may be found at:
There, you will find the following subdirectories:
Inside the processor type subdirectories the register utility is found.
Download it to your local system and mark it executable.
chmod a+x register
Then, run the register utility
./register
The utility is interactive and will prompt you for the type of product to be registered. Users of G.729 should first select "Digium Products" and then "G.729 Codec." At this point, you will be prompted to enter your G.729 key.
Please enter the key and press Enter or Return.
Following successful entry, the Digium License for use of the key will be displayed and you will be prompted to accept it.
If the license is accepted and the registration completed successfully, your key will be bound to your system, and you may restart Asterisk to begin making calls requiring G.729a.
Successful completion of the registration process will generate a .lic file that will be placed in the following directory:
/var/lib/asterisk/licenses/
Please backup the .lic file to a safe location that you can restore to your server if necessary. In the event that your system needs to have its distribution rebuilt or re-installed, it is NOT necessary to re-run the registration utility--provided that the hardware components have not changed. In this case, simply download the codec binary to the Asterisk modules directory and restore your backed-up copy of the .lic file to the Asterisk licenses directory.
To begin using your codec, please restart Asterisk.
Successful operation of the register utility requires the capability to create an outgoing TCP connection on port 443, the HTTPS port. If you do not have this capability, please contact your network administrator.
Successful completion of the registration process requires that your system have an "eth0" network device present. If this device is not present, registration cannot be completed.
The register utility binds itself to the MAC addresses of ALL available ethX devices. If your system has eth0 and eth1 devices during registration time, and you decide later to add an eth2 device in addition to eth0 and eth1, the codec will not load successfully when Asterisk is restarted. Adding or removing ethX interfaces will require a re-registration of your codec key.
The Asterisk CLI provides the following note: "Dropping extra frame of G.729 since we already have a VAD frame at the end." Digium G.729 supports G.729a ONLY. G.729b support is not provided by Asterisk. Please turn off VAD and Silence Suppression support on your endpoints connecting to Asterisk.
Your key is good for a maximum number of 2 registrations to unique Host IDs. Meaning, your key may be registered once to your first machine, and then once more should you need to change machines or change ethX devices in your machine. Your key is NOT good for unlimited activations. If you exceed your number of activations allowed, please contact Digium Support. Digium Support evaluates requests for additional activations on a case-by-case basis. Digium is under no responsibility to provide additional registrations.
Digium support may be contacted via e-mail at
So, you've received a free key for HPEC. Congratulations, and thanks for stopping by the booth! Your instructions to install HPEC are as follows:
Usage of HPEC requires three components: the HPEC binary, the register utility, and the zaphpec_enable utility.
There, you will find the a copy of the README file and the LICENSE file along with sub-directories for processor types, such as 32-bit and 64-bit. Users of 32-bit processors and distributions should choose the 32-bit directory. Users of 64-bit processors AND 64-bit distributions should choose 64-bit.
Inside these directories are zip files containing the HPEC binaries optimized for individual processor types. Contained in the name of each zip file is a versioning string, noted as, for example, 9.00.003. This notes Digium's release version of the HPEC binary.
The following are shown as an example of the 32-bit available builds:
The following are shown as an example of the 64-bit available builds:
Download the HPEC binary appropriate to your processor type, unzip its contents (which also contain a copy of the LICENSE file), and place the hpec_x86_XX.o_shipped binary into the hpec subdirectory of your Zaptel source; for example:
/usr/src/zaptel-1.2/hpec/
A Zaptel 'make' will automatically detect the presence of the hpec binary file and will, upon a rebuild, link it against the zaptel.ko kernel module; for example:
(Zaptel 1.2.x)
#make clean
#make install
(Zaptel 1.4.x)
#make clean
#./configure
#make install
Successful building of Zaptel with HPEC support can be noted from the system's dmesg or message log output during a kernel load of the Zaptel module, such as:
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.3
Zaptel Echo Canceller: Digium High-Performance Echo Canceller
Digium High-Performance Echo Canceller, version 9.00.003
Optimized for "opteron" CPU architecture
Coypright (C) 2006-2007 Digium, Inc. and Adaptive Digital Technologies, Inc.
This module is supplied under a commercial license granted by Digium, Inc.
Please see the full license text supplied by the accompanying
"register" utility, or ask for a copy from Digium.
If the Zaptel module is already loaded into your kernel, please reload it to affect these changes.
The next component required is Digium's register utility. The register utility may be found at:
There, you will find the following subdirectories:
Inside the processor type subdirectories the register utility is found.
Download it to your local system and mark it executable.
chmod a+x register
Then, run the register utility
./register
The utility is interactive and will prompt you for the type of product to be registered. Users of HPEC should first select "Digium Products" and then "High Performance Echo Can." At this point, you will be prompted to enter your HPEC key.
Please enter the key and press Enter or Return.
Following successful entry, the Digium License file for use of the key will be displayed and you will be prompted to accept it.
If the license is accepted and the registration completed successfully, your key will be bound to your system.
Inside the same HPEC directory on the Digium ftp site visited before, and again under the processor type subdirectories, along side of the HPEC binary processor zip files, are also utilities named:
zaphpec_enable
Please download the utility appropriate to your processor type. Users of 32-bit processor types and 32-bit distributions should download from the 32-bit directory. Users of 64-bit processor types AND 64-bit distributions should download from the 64-bit directory.
Once downloaded, move the utility to your binaries directory; for example:
/usr/bin
and then mark it executable.
chmod a+x /usr/bin/zaphpec_enable
Next, run the zaphpec_enable utility.
If successful, you will see a confirmation on the console.
In order to enable HPEC operation, the zaphpec_enable utility must be run following each kernel load of the zaptel.ko module. Meaning that, should you choose to have your system load the zaptel.ko module automatically at boot time, you will need to follow that with an execution of the zaphpec_enable utility in order for echo cancellation to occur. If the zaphpec_enable utility is not run, NO echo cancellation will be performed.
Successful completion of the registration process will generate a .lic file that will be placed in the following directory:
/var/lib/digium/licenses/
Please backup the .lic file to a safe location that you can restore to your server if necessary. In the event that your system needs to have its distribution rebuilt or re-installed, it is NOT necessary to re-run the register utility - provided that the hardware components have not changed. In this case, simply download the HPEC binary, rebuild Zaptel against it, and restore your backed-up copy of the .lic file to the Digium licenses directory.
Successful operation of the register utility requires the capability to create an outgoing TCP connection on port 443, the HTTPS port. If you do not have this capability, please contact your network administrator.
Successful completion of the registration process requires that your system have an "eth0" network device present. If this device is not present, registration cannot be completed.
The register utility binds itself to the MAC addresses of ALL available ethX devices. If your system has eth0 and eth1 devices during registration time, and you decide later to add an eth2 device in addition to eth0 and eth1, the HPEC binary will not load successfully when Asterisk is restarted. Adding or removing ethX interfaces will require a re-registration of your HPEC key.
Your key is good for a maximum number of 2 registrations to unique Host IDs. Meaning, your key may be registered once to your first machine, and then once more should you need to change machines or change ethX devices in your machine. Your key is NOT good for unlimited activations. If you exceed your number of activations allowed, please contact Digium Support. Digium Support evaluates requests for additional activations on a case-by-case basis. Digium is under no responsibility to provide additional registrations.
Digium support may be contacted via e-mail at
