Can you tell if there are any know issues running OpenVZ on a 64bit system?
I have OpenVZ installed on two different HN, one is running CentOS 32bit and the other CentOS 64bit. On the HN running the 32bit OS the meetme works fine following the procedure described below but not on the HN running the 64bit OS.
Let me explain what's happening:
I created an elastix template on the 32bit machine and have loaded the Dahdi (Zaptel) modules by adapting the information provided at http://wiki.openvz.org/Asterisk_from_source as follows:
Start the Service on the HN
Load the Dahdi Modules on the HN
modprobe dahdi
modprobe dahdi_dummy
Grant the VE Access to the Devices
vzctl set 120 --devnodes dahdi/pseudo:rw --save
vzctl set 120 --devnodes dahdi/channel:rw --save
vzctl set 120 --devnodes dahdi/timer:rw --save
vzctl set 120 --devnodes dahdi/ctl:rw --save
Set the owner and group to be asterisk
vzctl exec 120 chown -R asterisk:asterisk /dev/dahdi /lib/udev/devices/dahdi
Now on 32bit machine the conferencing working it works fine at least until the VPS is rebooted!
However, when I transfer a copy of the same template over to the 64bit machine and try the same identical procedure followed to get the conferencing working the call connects but there is no audio for the meetme or audio for any IVR or anything else.
Only when I delete the /dev/dahdi/timer and /lib/udev/devices/dahdi/timer the audio works again. However, I get the message that the conference PIN is not valid when I try to connect to a conference.
Any ideas?
regards,
Sammy08
[Updated on: Fri, 03 April 2009 15:45]
Report message to a moderator
OpenVZ Forum
Members
Search
Help
Register
Login
Home
