12
edits
Changes
how to compile asterisk inside CT
Asterisk is free and open source code to create software PBX server. See [http://www.asterisk.org] for details.
This package perfectly runs in side OpenVZ container. Some users run up to 60 containers with Asterisk deployed for
production per single hardware node. Although the easiest way to install Asterisk into container is to use pre-build package
from Linux distribution, occasionally one may need to have a possibility to build it from source tarball available on developer's site.
In order to do it the following remarks are worth reading:
Asterisk PBX server itself is compiled out of the shelf in CT provided that develop application template is installed for this CT.
The functionality of the resulting executable is enough to support simple VoIP telephony.
Unfortunately, one particular module called MeetMe (conferencing tool) will be switched off from compilation. This happens due to external dependency on 'zaptel' package.
This package provides support for some hardware cards for FXO/FXS analog telephony marketed by Digium (the company behind Asterisk), and on top of that supplies so called ztdummy kernel module. Ztdummy works like a simple metronome which is required to synchronize multiple sound streams in case of conference call. Initially this module requires 1 kHz clock which is avail for example on all Digium cards.
If you do not have this card (or equivalent from other vendors) as in case if you do not plan to use analog telephone lines, nothing is lost. You just need to play a little trick with Asterisk make system and HN ovz kernel.
First one needs to download zaptel tarball from the same location as Asterisk itself, and copy it's header zaptel.h to location
/usr/include/zaptel/zaptel.h in the CT where you plan to build Asterisk. This tweaks MeetMe for installation. Then you need to build
ztdummy.ko in HN and make it auto-loaded.
Below is an example of how to install Asterisk into OpenVZ VE based on debian stable aka. "sarge":
