| Asterisk Meetme and Dahdi (Zaptel) issue on 64bit HN [message #35554] |
Fri, 03 April 2009 14:45  |
sammy08
Messages: 21
Registered: April 2008
|
Junior Member |
|
|
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 |
|
|
|
|
|
|
|
| Re: Asterisk Meetme and Dahdi (Zaptel) issue on 64bit HN [message #35577 is a reply to message #35576] |
Mon, 06 April 2009 10:31  |
sammy08
Messages: 21
Registered: April 2008
|
Junior Member |
|
|
| maratrus wrote |
Hi Errol,
do you use the same template on the 64-bit HN as you use on the 32-bit HN? (i.e. 32-bit template on the 64-bit HN)
|
The template was a 32bit template built on a 32bit machine and copied over to the 64bit machine.
| maratrus wrote |
Make sure that all devices inside /dev/dahdi directory have been created with appropriate major and minor numbers.
|
I am not sure what you mean by "appropriate major and minor numbers" but the devices [pseudo, channel, ctl, timer] have been created on the VE.
| maratrus wrote |
Does the message
[Apr 5 16:56:42] WARNING[16155] app_meetme.c: Unable to open pseudo device
appears during dahdi service starting?
|
Dahdi starts fine. That message appears when trying to start Asterisk.
I applied the patch as per advice here on the HN: http://bugs.digium.com/view.php?id=13930&nbn=20
I tried to applied to the VE, am I meant to recompile Asterisk after?
[Updated on: Mon, 06 April 2009 10:35] Report message to a moderator |
|
|
|
|
|
| Re: Asterisk Meetme and Dahdi (Zaptel) issue on 64bit HN [message #35579 is a reply to message #35578] |
Mon, 06 April 2009 11:34 |
sammy08
Messages: 21
Registered: April 2008
|
Junior Member |
|
|
Here is what I have done so far.
I copied the patched dahdi_dummy files over to the VE, then downloaded and compiled Asterisk. After I tried to start dahdi I got the errors below.
[root@testpbx dahdi]# service dahdi start
Loading DAHDI hardware modules:
WARNING: Error inserting crc_ccitt (/lib/modules/2.6.18-92.1.18.el5.028stab060.8/kernel/lib/crc-ccitt.ko): Operation not permitted
FATAL: Error inserting dahdi (/lib/modules/2.6.18-92.1.18.el5.028stab060.8/dahdi/dahdi.ko): Operation not permitted
No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: Notice: Configuration file is /etc/dahdi/system.conf
line 0: Unable to open master device '/dev/dahdi/ctl'
1 error(s) detected
Afterwards I once again copied the devices back over to the VE as follows:
On the HN
[root@myserver dahdi]# for x in `ls /dev/dahdi`; do /usr/sbin/vzctl set 130 --devnodes dahdi/${x}:rw --save; done
Setting devices
Saved parameters for CT 130
Setting devices
Saved parameters for CT 130
Setting devices
Saved parameters for CT 130
Setting devices
Saved parameters for CT 130
[root@myserver dahdi]#
[root@myserver dahdi]# vzctl exec 130 chown -R asterisk /dev/dahdi /lib/udev/devices/dahdi
[root@myserver dahdi]# vzctl exec 130 chgrp -R asterisk /dev/dahdi /lib/udev/devices/dahdi
[root@myserver dahdi]#
On the VE
[root@testpbx dahdi]# service dahdi start
Loading DAHDI hardware modules:
WARNING: Error inserting crc_ccitt (/lib/modules/2.6.18-92.1.18.el5.028stab060.8/kernel/lib/crc-ccitt.ko): Operation not permitted
FATAL: Error inserting dahdi (/lib/modules/2.6.18-92.1.18.el5.028stab060.8/dahdi/dahdi.ko): Operation not permitted
No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]
[root@testpbx dahdi]#
Then I try to start Asterisk on the VE
[root@testpbx dahdi]# service asterisk restart
Shutting down asterisk: [FAILED]
Starting asterisk: [ OK ]
[root@testpbx dahdi]# Asterisk ended with exit status 1
Asterisk died with code 1.
Automatically restarting Asterisk.
mpg123: no process killed
Asterisk ended with exit status 1
Asterisk died with code 1.
[Updated on: Mon, 06 April 2009 11:35] Report message to a moderator |
|
|
|
|
|
| Re: Asterisk Meetme and Dahdi (Zaptel) issue on 64bit HN [message #37706 is a reply to message #35554] |
Tue, 13 October 2009 08:55 |
mustardman
Messages: 91
Registered: October 2009
|
Member |
|
|
The problem is that you cannot run Dahdi(zaptel) in a 32bit VM on 64bit OpenVZ HN. Both have to be 32 bit or 64bit which makes sense considering Dahdi (zaptel) has to be installed on the HN.
The guys as Pbx-in-a-flash have all come to this conclusion. There is a long thread about it over there.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
