Here is a howto on installing Elastix 2.0 in a vm under OpenVZ / Proxmox:

#Download, compile, and install dahdi on hardware node

#Download a Centos 5.4 template for the same platform the hardware node is 32/64 bit
cd /var/lib/vz/template/cache
wget download.openvz.org/template/precreated/centos-5-x86_64.tar.gz

#Start vm and give it access to the /dev folder
vzctl start $VID
vzctl set $VID --devnodes dahdi/channel:rw --save
vzctl set $VID --devnodes dahdi/ctl:rw --save
vzctl set $VID --devnodes dahdi/timer:rw --save
vzctl set $VID --devnodes dahdi/pseudo:rw --save
vzctl set $VID --devnodes null:rw --save

#Download Elastix 2.0, mount on hardware node, and copy the folder to the vm
cd /var/lib/vz/template/iso/
wget downloads.sourceforge.net/project/elasti...64-bin-07ago2010.iso
mkdir /mnt/Elastix
mount -t iso9660 -o loop /var/lib/vz/template/iso/Elastix-2.0.1-x86_64-bin-07ago2010.iso /mnt/Elastix
cp -R /mnt/Elastix /var/lib/vz/private/$VID/usr/src

#Enter vm and configure below:
ifconfig eth0 192.168.128.12/24
route add default gw 192.168.128.1

yum -y install createrepo
createrepo /usr/src/Elastix

echo '
[local]
enabled = 1
name = Elastix
baseurl = file:///usr/src/Elastix
gpgcheck = 0
' > /etc/yum.repos.d/elastix.repo

yum -y update

yum -y install asterisk* elastix-* freeze fxload libmfcr2 lzop perl-HTML-TokeParser-Simple perl-WWW-Mechanize mod_ssl mlocate gcc gcc-c++ system-config-network-tui wget sox nano

mv -f /etc/yum.repos.d/elastix.repo.rpmnew /etc/yum.repos.d/elastix.repo

yum clean all

sed -i 's/TTY=9/#TTY=9/g' /usr/sbin/safe_asterisk
sed -i 's/chown asterisk \/dev\/tty9/#chown asterisk \/dev\/tty9/g' /etc/init.d/asterisk
sed -i 's/\/sbin\/start_udev/#\/sbin\/start_udev/g' /etc/rc.d/rc.sysinit
sed -i 's/\/usr\/sbin\/fxotune -s/#\/usr\/sbin\/fxotune -s/g' /etc/rc.local
sed -i 's/chown $AMPASTERISKUSER \/dev\/tty9/#chown $AMPASTERISKUSER \/dev\/tty9/g' /var/lib/asterisk/bin/freepbx_engine

chkconfig haldaemon off
chkconfig asterisk off
chkconfig dahdi off
chkconfig wanrouter off

rm -rf /etc/init.d/dahdi
rm -rf /etc/init.d/wanrouter
rm -rf /usr/src/Elastix

echo 'DEVICE=eth0' > /etc/sysconfig/network-scripts/ifcfg-eth0
system-config-network

service mysqld start
/etc/rc3.d/S66elastix-firstboot start

reboot

yum -y update

################

I also have a 64 built template for download:
docs.google.com/uc?id=0B8T1zyMjIRDgMjBjM...t=download&hl=en

You must run below and reboot on first boot:
/etc/rc3.d/S66elastix-firstboot start

Have fun,
Gil

have you managed to get PCI passthrough working for your FXO cards?

I have only got a redfone bridge to work with the dahdi drivers installed on the host server.

I wouldn't recommend a TDM card to be installed into a OpenVZ server with out the know how and testing to add the /proc/dahdi or /proc/zaptel file access to the server. I have also seen people reference the need access to the /dev folder, but I didn't need it using the redfone bridge.

You definitely need to give access to the /proc/dahdi or /proc/zaptel for accurate time source for the meetme app, which a lot of features use like call park.

I would recommend using a quality FXO gateway like Audiocodes for FXO termination. If you have a lot more lines to support, redfone bridge works for T1/E1 (still haven't tried a TDM card internally), or just use a really good SIP provider with a QoS/MPLS provisioned circuit designed for VoIP.

I have only got a redfone bridge to work with the dahdi drivers installed on the host server.

I wouldn't recommend a TDM card to be installed into a OpenVZ server with out the know how and testing to add the /proc/dahdi or /proc/zaptel file access to the server. I have also seen people reference the need access to the /dev folder, but I didn't need it using the redfone bridge.

You definitely need to give access to the /proc/dahdi or /proc/zaptel for accurate time source for the meetme app, which a lot of features use like call park.

I would recommend using a quality FXO gateway like Audiocodes for FXO termination. If you have a lot more lines to support, redfone bridge works for T1/E1 (still haven't tried a TDM card internally), or just use a really good SIP provider with a QoS/MPLS provisioned circuit designed for VoIP.

Hi,

Just done:

I also have a 64 built template for download:
docs.google.com/uc?id=0B8T1zyMjIRDgMjBjM...t=download&hl=en

You must run below and reboot on first boot:
/etc/rc3.d/S66elastix-firstboot start

Installed on proxmox template and all is good - calls terminate through freepbx but when I implicate the a2billing outbound trunk I get the "all circuits are busy - please try your call again later"
take the a2billing back out of the equation and it all works
The problem is something to do with passing the call to a2billing.
I have even tried following steps listed here: sysadminman.net/blog/2010/create-a-custo...-with-a2billing-1282 with the outbound route as Local/$OUTNUM$@a2billing/n but still no luck.

Any ideas ????

John

I don't use a2billing, so I can't help you on that.

But, this template was based on 2.0.1 of Elastix, so you might want to update the system, along with search the forums for the same problem in the a2billing section for Elastix 2.0.1.