OpenVZ Forum


Home » General » Support » *SOLVED* Zaptel - ztdummy - kernel install help
Re: Zaptel - ztdummy - kernel install help [message #41459 is a reply to message #26593] Wed, 26 January 2011 11:55 Go to previous messageGo to previous message
maxglucksmann is currently offline  maxglucksmann
Messages: 2
Registered: January 2011
Location: Miami
Junior Member

Hello Kirill,

Wanted to write you because I've tried several times with the ovzkernel and ovzkernel-devel compiling also zaptel and still can't start ztdummy nor zaptel's init.d service in the CN. I've replaced the number values for security...
____________________________________________________________ _


____________________________________________________________ _
This is the kernel setup and ovz packages:

HN:
[root@box src]# rpm -qa | grep -i ovz
ovzkernel-devel-2.6.18-194.3.1.el5.028stab069.6
ovzkernel-2.6.18-194.3.1.el5.028stab069.6

uname -a
Linux box.astraqom.ca 2.6.18-194.3.1.el5.028stab069.6 #1 SMP Wed May 26 18:31:05 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux

CN:
[root@pickering ~]# rpm -qa | grep -i ovz
ovzkernel-2.6.18-194.3.1.el5.028stab069.6
ovzkernel-devel-2.6.18-194.3.1.el5.028stab069.6

uname -a
Linux pickering 2.6.18-194.3.1.el5.028stab069.6 #1 SMP Wed May 26 18:31:05 MSD 2010 i686 i686 i386 GNU/Linux
____________________________________________________________ _


____________________________________________________________ _
Besides that, in the HN is working properly - after doing:
make distclean
make clean
./configure
make menuselect (may be needed to be run twice, select only ztdummy)
make

FAILS
...
...
...
include/linux/hardirq.h:38:27: warning: "NR_IRQS" is not defined
make[3]: *** [/usr/src/comtelpbx-3.0/asterisk/zaptel-1.4.12.1/kernel/pcir adio.o] Error 1
make[2]: *** [_module_/usr/src/comtelpbx-3.0/asterisk/zaptel-1.4.12.1/ker nel] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.18-194.3.1.el5.028stab069.6-i686'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/comtelpbx-3.0/asterisk/zaptel-1.4.12.1'
make: *** [all] Error 2
____________________________________________________________ _


____________________________________________________________ _
After changing the ovzkernel and ovzkernel-devel packages:
rhel5-2.6.18/028stab069.6/


[root@box ovzkernel]# rpm -Uvh ovzkernel-2.6.18-194.3.1.el5.028stab069.6.x86_64.rpm
Preparing... ########################################### [100%]
1:ovzkernel ########################################### [100%]

[root@box ovzkernel]# rpm -Uvh ovzkernel-devel-2.6.18-194.3.1.el5.028stab069.6.x86_64.rpm Preparing... ########################################### [100%]
1:ovzkernel-devel ########################################### [100%]

make distclean
make clean
make menuselect (twice)
select only ztdummy
make
make install

[root@box zaptel-1.4.12.1]# make config
install -D zaptel.init /etc/rc.d/init.d/zaptel
install -D ifup-hdlc /etc/sysconfig/network-scripts/ifup-hdlc
/sbin/chkconfig --add zaptel
Zaptel has been configured.

If you have any zaptel hardware it is now recommended to
edit /etc/default/zaptel or /etc/sysconfig/zaptel and set there an
optimal value for the variable MODULES .

I think that the zaptel hardware you have on your system is:

...
...
...

[root@box zaptel-1.4.12.1]# service zaptel restart
Unloading zaptel hardware drivers:.
Loading zaptel framework: FATAL: Error inserting zaptel (/lib/modules/2.6.18-194.3.1.el5.028stab069.6/misc/zaptel.ko ): Invalid module format
[FAILED]
Waiting for zap to come online...OK
Loading zaptel hardware modules:Running ztcfg: ioctl(ZT_LOADZONE) failed: Invalid argument
Notice: Configuration file is /etc/zaptel.conf
line 287: Unable to register tone zone 'us'
[ OK ]
____________________________________________________________ _



____________________________________________________________ _
Devices:
[root@box zaptel-1.4.12.1]# ls -lsa /dev/zap/
total 0
0 drwxr-xr-x 2 root root 140 Jan 25 20:01 .
0 drwxr-xr-x 14 root root 14440 Jan 26 01:06 ..
0 crw-rw---- 1 root root 196, 254 Jan 25 20:01 channel
0 crw-rw---- 1 root root 196, 0 Jan 25 20:01 ctl
0 crw-rw---- 1 root root 196, 255 Jan 25 20:01 pseudo
0 crw-rw---- 1 root root 196, 253 Jan 25 20:01 timer
0 crw-rw---- 1 root root 196, 250 Jan 25 20:01 transcode
[root@box zaptel-1.4.12.1]#
____________________________________________________________ _



____________________________________________________________ _
Port devices:
[root@box ~]# vzctl set 999888777 --devnodes zap/transcode:rw --save
Setting devices
Saved parameters for CT 999888777
[root@box ~]# vzctl set 999888777 --devnodes zap/timer:rw --save
Setting devices
Saved parameters for CT 999888777
[root@box ~]# vzctl set 999888777 --devnodes zap/pseudo:rw --save
Setting devices
Saved parameters for CT 999888777
[root@box ~]# vzctl set 999888777 --devnodes zap/ctl:rw --save
Setting devices
Saved parameters for CT 999888777
[root@box ~]# vzctl set 999888777 --devnodes zap/channel:rw --save
Setting devices
Saved parameters for CT 999888777
____________________________________________________________ _



____________________________________________________________ _

Still, when I'm called into a conference by vicidial's agent gui, the application app_meetme is run and the CLI says...

pseudo channel is not available:

== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing [123123123@default:1] MeetMe("SIP/sip1000001-09654350", "123123123|F") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
== Parsing '/etc/asterisk/meetme-vicidial.conf': Found
[Jan 26 14:47:15] WARNING[24346]: app_meetme.c:800 build_conf: Unable to open pseudo device
== Manager 'sendcron' logged off from 127.0.0.1
-- <SIP/sip1000001-09654350> Playing 'conf-invalid' (language 'en')
== Spawn extension (default, 123123123, 1) exited non-zero on 'SIP/sip1000001-09654350'
-- Executing [h@default:1] DeadAGI("SIP/sip1000001-09654350", " agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG---- -16---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG---- -16--------------- completed, returning 0
pickering*CLI>
____________________________________________________________ _


Any advice you could give will be very appreciated.

Thank you very much and have a good day,
Max Glucksmann
Mobility1 LLC
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: iptables error?
Next Topic: vzctl stop kills glusterfs?
Goto Forum:
  


Current Time: Sat Aug 02 12:57:12 GMT 2025

Total time taken to generate the page: 0.52936 seconds