*SOLVED* Make Kernel Module ztdummy available in VE [message #16155] |
Fri, 24 August 2007 12:55  |
schogge
Messages: 19 Registered: July 2007
|
Junior Member |
|
|
Hi,
I have installed and loaded the kernel module ztdummy (include in zaptel) on HN and want to give VE access to it.
My system:
Host: CentOS 5
Kernel: 2.6.18-8.1.4.el5.028stab035.1
Guest: CentOS 4
zaptel: zaptel-1.2.20.1
The test utility zttest shows this on HN:
# zttest
Opened pseudo zap interface, measuring accuracy...
99.975586% 99.926758% 99.975586% 99.975586% 99.926758%
I also gave VE access to /dev/zap by running
for x in `ls /dev/zap`; do /usr/sbin/vzctl set 200 --devnodes zap/${x}:rw --save; done
ls /dev/zap inside VE shows
ls /dev/zap/
channel ctl pseudo timer transcode
However asterisk is compiling without its conferencing tool MeetMe, which means ztdummy is missing on the system.
Is their a way to check if ztdummy works correctly in VE?
Any idea to get it running?
Thanks,
schogge
[Updated on: Fri, 21 December 2007 07:25] by Moderator Report message to a moderator
|
|
|
Re: Make Kernel Module ztdummy available in VE [message #21296 is a reply to message #16155] |
Thu, 04 October 2007 15:01   |
Alexandr Andreev
Messages: 35 Registered: October 2006
|
Member |
|
|
1. Had you solve the problem?
Quote: | However asterisk is compiling without its conferencing tool MeetMe, which means ztdummy is missing on the system.
|
2. Probably you compiled zaptel in VE0, installed kernel modules, gave access to /dev/zap to VE's, and then entered VE, and tried to compile asteriks.
If so, you should also build and install zaptel inside VE, because asterisk requires zaptel headers and libraries to enable MeetMe support.
3. To check whether ztdummy loaded successful, run in your VE
# ztcfg -v
# ztcfg -d
# cat /proc/zaptel/1
Here is all asterisk features, depending on ZAPTEL:
# grep ZAPTEL menuselect.makedeps
MENUSELECT_DEPENDS_app_flash=ZAPTEL
MENUSELECT_DEPENDS_app_meetme=ZAPTEL
MENUSELECT_DEPENDS_app_page=ZAPTEL APP_MEETME
MENUSELECT_DEPENDS_app_rpt=ZAPTEL TONEZONE
MENUSELECT_DEPENDS_app_zapbarge=ZAPTEL
MENUSELECT_DEPENDS_app_zapras=ZAPTEL
MENUSELECT_DEPENDS_app_zapscan=ZAPTEL
MENUSELECT_DEPENDS_chan_iax2=ZAPTEL
MENUSELECT_DEPENDS_chan_zap=RES_SMDI ZAPTEL_VLDTMF ZAPTEL TONEZONE PRI
MENUSELECT_DEPENDS_codec_zap=ZAPTEL_TRANSCODE ZAPTEL
MENUSELECT_DEPENDS_res_musiconhold=ZAPTEL
|
|
|
|
Re: Make Kernel Module ztdummy available in VE [message #23400 is a reply to message #23388] |
Fri, 16 November 2007 10:48   |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
Well, loading modules from inside VE is prohibited, you have to load modules from HN (Hardware Node).
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
|
|
|
|
Re: Make Kernel Module ztdummy available in VE [message #26587 is a reply to message #21296] |
Tue, 29 January 2008 08:13  |
ricoche
Messages: 17 Registered: January 2008 Location: Nagano Japan
|
Junior Member |
|
|
Alexandr Andreev wrote on Thu, 04 October 2007 11:01 |
2. Probably you compiled zaptel in VE0, installed kernel modules, gave access to /dev/zap to VE's, and then entered VE, and tried to compile asteriks.
If so, you should also build and install zaptel inside VE, because asterisk requires zaptel headers and libraries to enable MeetMe support.
|
This is exactly what I did, but I am not sure how to install zaptel inside VE because it requires access to the Kernel souce which I can't seem to install using "yum install ovzkernel-devel". I did this on the HN and it worked, but what to do with regards to the VE I am unsure.
Thanks,
Jim
|
|
|