Page 1 of 1

64bit GoAutoDial

PostPosted: Sat Feb 25, 2012 2:15 pm
by gardo
64 bit version of GoAutoDial!

http://goautodial.org/projects/goautodialce/wiki/64bit

Using the instructions from above, one can install GoAutoDial on a vanilla CentOS 5.X 64bit system (with a few simple commands). Very handy for those wanting to use GoAutoDial on rented or hosted servers. 8)

PostPosted: Wed Mar 28, 2012 10:07 pm
by enavaro
4. Install Asterisk and Dahdi packages

yum install asterisk asterisk-perl dahdi-linux dahdi-tools kmod-dahdi-linux \
asterisk-sounds-core-en-alaw asterisk-sounds-core-en-gsm asterisk-sounds-core-en-ulaw \
asterisk-sounds-extra-en-alaw asterisk-sounds-extra-en-gsm asterisk-sounds-extra-en-ulaw

I'm stuck with this error:

[root@cloud ~]# yum install asterisk asterisk-perl dahdi-linux dahdi-tools kmod-dahdi-linux \
> asterisk-sounds-core-en-alaw asterisk-sounds-core-en-gsm asterisk-sounds-core-en-ulaw \
> asterisk-sounds-extra-en-alaw asterisk-sounds-extra-en-gsm asterisk-sounds-extra-en-ulaw
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.averse.net
* extras: mirror.averse.net
* updates: mirror.averse.net
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package asterisk.x86_64 0:1.4.39.1-vici.go set to be updated
--> Processing Dependency: libpri >= 1.4.7 for package: asterisk
--> Processing Dependency: speex for package: asterisk
--> Processing Dependency: libpri.so.1.4()(64bit) for package: asterisk
--> Processing Dependency: libtonezone.so.2.0()(64bit) for package: asterisk
--> Processing Dependency: libgsm.so.1()(64bit) for package: asterisk
---> Package asterisk-perl.x86_64 0:0.08-1.go set to be updated
---> Package asterisk-sounds-core-en-alaw.noarch 0:1.4.21-1_centos5 set to be updated
---> Package asterisk-sounds-core-en-gsm.noarch 0:1.4.21-1_centos5 set to be updated
---> Package asterisk-sounds-core-en-ulaw.noarch 0:1.4.21-1_centos5 set to be updated
---> Package asterisk-sounds-extra-en-alaw.noarch 0:1.4.11-1_centos5 set to be updated
---> Package asterisk-sounds-extra-en-gsm.noarch 0:1.4.11-1_centos5 set to be updated
---> Package asterisk-sounds-extra-en-ulaw.noarch 0:1.4.11-1_centos5 set to be updated
---> Package dahdi-linux.x86_64 0:2.5.0.1-1_centos5 set to be updated
--> Processing Dependency: dahdi-firmware for package: dahdi-linux
--> Processing Dependency: yum-kmod for package: dahdi-linux
---> Package dahdi-tools.x86_64 0:2.5.0.1-1_centos5 set to be updated
---> Package kmod-dahdi-linux.x86_64 0:2.5.0.1-1_centos5.2.6.18_274.3.1.el5.go set to be installed
--> Processing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5.go for package: kmod-dahdi-linux
--> Running transaction check
---> Package dahdi-firmware.noarch 0:2.0.3-1_centos5 set to be updated
--> Processing Dependency: dahdi-firmware-oct6114-064 = 1.05.01 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-oct6114-128 = 1.05.01 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-hx8 = 2.06 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-vpmoct032 = 1.11.0 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-tc400m = MR6.12 for package: dahdi-firmware
--> Processing Dependency: dahdi-linux-fwload-vpmadt032-kmod for package: dahdi-firmware
---> Package gsm.x86_64 0:1.0.13-1.el5.rf set to be updated
---> Package kernel.x86_64 0:2.6.18-274.3.1.el5.go set to be installed
---> Package libpri.x86_64 0:1.4.11.5-1_centos5 set to be updated
---> Package libtonezone.x86_64 0:2.5.0.1-1_centos5 set to be updated
---> Package speex.x86_64 0:1.0.5-4.el5_1.1 set to be updated
---> Package yum-kmod.noarch 0:1.1.16-21.el5.centos set to be updated
--> Running transaction check
---> Package dahdi-firmware-hx8.noarch 0:2.06-1_centos5 set to be updated
---> Package dahdi-firmware-oct6114-064.noarch 0:1.05.01-1_centos5 set to be updated
---> Package dahdi-firmware-oct6114-128.noarch 0:1.05.01-1_centos5 set to be updated
---> Package dahdi-firmware-tc400m.noarch 0:MR6.12-1_centos5 set to be updated
---> Package dahdi-firmware-vpmoct032.noarch 0:1.11.0-1_centos5 set to be updated
---> Package kmod-dahdi-linux-fwload-vpmadt032.x86_64 0:2.5.0.1-1_centos5.2.6.18_274.3.1.el5 set to be installed
--> Processing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5 for package: kmod-dahdi-linux-fwload-vpmadt032
--> Finished Dependency Resolution
kmod-dahdi-linux-fwload-vpmadt032-2.5.0.1-1_centos5.2.6.18_274.3.1.el5.x86_64 from goautodial-current has depsolving problems
--> Missing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5 is needed by package kmod-dahdi-linux-fwload-vpmadt032-2.5.0.1-1_centos5.2.6.18_274.3.1.el5.x86_64 (goautodial-current)
Error: Missing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5 is needed by package kmod-dahdi-linux-fwload-vpmadt032-2.5.0.1-1_centos5.2.6.18_274.3.1.el5.x86_64 (goautodial-current)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
[root@cloud ~]#

Any turn around commands?

PostPosted: Mon Apr 02, 2012 5:39 pm
by gardo
What's the CentOS base version you're using?

PostPosted: Mon Apr 02, 2012 11:54 pm
by enavaro
Centos 5.7 because your guide recommend 5.7 version. I downloaded the ISO from Centos.org archive.

Can I use Centos 5.8 and follow your guide?

PostPosted: Tue Apr 03, 2012 5:25 pm
by gardo
Yeah. We never had problems with CentOS 5.7 64bit. That's the base distro we are using. We'll try to simulate and see what's happening.

PostPosted: Wed Apr 04, 2012 12:20 pm
by chinita17
any result for 64 bit on centos 5.8 distro... im stucked on this:

Setting up Install Process
Package asterisk-sounds-core-en-alaw-1.4.21-1_centos5.noarch already installed and latest version
Package asterisk-sounds-core-en-gsm-1.4.21-1_centos5.noarch already installed and latest version
Package asterisk-sounds-core-en-ulaw-1.4.21-1_centos5.noarch already installed and latest version
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.
--> Running transaction check
---> Package asterisk.x86_64 0:1.4.39.1-vici.go set to be updated
--> Processing Dependency: libpri >= 1.4.7 for package: asterisk
--> Processing Dependency: speex for package: asterisk
--> Processing Dependency: libpri.so.1.4()(64bit) for package: asterisk
--> Processing Dependency: libtonezone.so.2.0()(64bit) for package: asterisk
--> Processing Dependency: libgsm.so.1()(64bit) for package: asterisk
---> Package asterisk-perl.x86_64 0:0.08-1.go set to be updated
---> Package asterisk-sounds-extra-en-alaw.noarch 0:1.4.11-1_centos5 set to be updated
---> Package asterisk-sounds-extra-en-gsm.noarch 0:1.4.11-1_centos5 set to be updated
---> Package asterisk-sounds-extra-en-ulaw.noarch 0:1.4.11-1_centos5 set to be updated
---> Package dahdi-linux.x86_64 0:2.5.0.1-1_centos5 set to be updated
--> Processing Dependency: dahdi-firmware for package: dahdi-linux
--> Processing Dependency: yum-kmod for package: dahdi-linux
---> Package dahdi-tools.x86_64 0:2.5.0.1-1_centos5 set to be updated
---> Package kmod-dahdi-linux.x86_64 0:2.5.0.1-1_centos5.2.6.18_274.3.1.el5.go set to be installed
--> Processing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5.go for package: kmod-dahdi-linux
--> Running transaction check
---> Package dahdi-firmware.noarch 0:2.0.3-1_centos5 set to be updated
--> Processing Dependency: dahdi-firmware-oct6114-064 = 1.05.01 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-oct6114-128 = 1.05.01 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-hx8 = 2.06 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-vpmoct032 = 1.11.0 for package: dahdi-firmware
--> Processing Dependency: dahdi-firmware-tc400m = MR6.12 for package: dahdi-firmware
--> Processing Dependency: dahdi-linux-fwload-vpmadt032-kmod for package: dahdi-firmware
---> Package gsm.x86_64 0:1.0.13-1.el5.rf set to be updated
---> Package kernel.x86_64 0:2.6.18-274.3.1.el5.go set to be installed
---> Package libpri.x86_64 0:1.4.11.5-1_centos5 set to be updated
---> Package libtonezone.x86_64 0:2.5.0.1-1_centos5 set to be updated
---> Package speex.x86_64 0:1.0.5-4.el5_1.1 set to be updated
---> Package yum-kmod.noarch 0:1.1.16-21.el5.centos set to be updated
--> Running transaction check
---> Package dahdi-firmware-hx8.noarch 0:2.06-1_centos5 set to be updated
---> Package dahdi-firmware-oct6114-064.noarch 0:1.05.01-1_centos5 set to be updated
---> Package dahdi-firmware-oct6114-128.noarch 0:1.05.01-1_centos5 set to be updated
---> Package dahdi-firmware-tc400m.noarch 0:MR6.12-1_centos5 set to be updated
---> Package dahdi-firmware-vpmoct032.noarch 0:1.11.0-1_centos5 set to be updated
---> Package kmod-dahdi-linux-fwload-vpmadt032.x86_64 0:2.5.0.1-1_centos5.2.6.18_274.3.1.el5 set to be installed
--> Processing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5 for package: kmod-dahdi-linux-fwload-vpmadt032
--> Finished Dependency Resolution
kmod-dahdi-linux-fwload-vpmadt032-2.5.0.1-1_centos5.2.6.18_274.3.1.el5.x86_64 from goautodial-current has depsolving problems
--> Missing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5 is needed by package kmod-dahdi-linux-fwload-vpmadt032-2.5.0.1-1_centos5.2.6.18_274.3.1.el5.x86_64 (goautodial-current)
Error: Missing Dependency: kernel-x86_64 = 2.6.18-274.3.1.el5 is needed by package kmod-dahdi-linux-fwload-vpmadt032-2.5.0.1-1_centos5.2.6.18_274.3.1.el5.x86_64 (goautodial-current)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.

PostPosted: Wed Apr 04, 2012 3:19 pm
by Op3r
Here's the keyword

There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.
--> Running transaction check

Re: 64bit GoAutoDial

PostPosted: Fri Apr 27, 2012 1:54 am
by gardo
Forgot to update this thread. This should be good to go. Let us know how it goes.

Re: 64bit GoAutoDial

PostPosted: Thu Jul 19, 2012 11:23 am
by cbsys
There is no corresponding Asterisk-devel rpm to go with this in the repo.
Hence there is no way of compiling any additional asterisk modules, such as app_swift to enable TTS

Any chance of making asterisk-devel available in the 64-bit repo too?

Re: 64bit GoAutoDial

PostPosted: Wed Aug 01, 2012 2:55 pm
by gers55
Hi Guys

I am having issues downloading the 64bit image for centos 6 . The rpms are not available . I take it i cannot get the 64bit image on this centos version

Re: 64bit GoAutoDial

PostPosted: Wed Aug 08, 2012 2:39 pm
by gardo
CentOS 6.X is not yet supported. The RPMs are for CentOS 5.6 and up.

Re: 64bit GoAutoDial

PostPosted: Fri Sep 07, 2012 6:03 pm
by bryan.kewl
I am getting following error when trying to install on CentOS 5.7 64-bit.
Transaction Check Error:
package kernel-2.6.18-274.7.1.el5.x86_64 (which is newer than kernel-2.6.18-274.3.1.el5.go.x86_64) is already installed

Re: 64bit GoAutoDial

PostPosted: Sat Sep 08, 2012 12:16 am
by chrisdbarnett
bryan.kewl wrote:I am getting following error when trying to install on CentOS 5.7 64-bit.
Transaction Check Error:
package kernel-2.6.18-274.7.1.el5.x86_64 (which is newer than kernel-2.6.18-274.3.1.el5.go.x86_64) is already installed


I have the same problem on Centos 5.8

I'm trying out the following:

yum install kernel-2.6.18

Which appears to have installed 2.6.18.308

Which I'm hoping is good enough.....

my /boot/grub.conf looks in order...

Re: 64bit GoAutoDial

PostPosted: Sat Sep 08, 2012 12:26 am
by chrisdbarnett
Bear with me....just testing out kernel-2.6.18-274.3.1.el5.x86_64.rpm....

Re: 64bit GoAutoDial

PostPosted: Sat Sep 08, 2012 12:55 am
by chrisdbarnett
OK...got there in the end!

You have to downgrade it

yum install kernel-2.6.18-274.3.1.el5.x86_64 should do.

Then reboot. Tidy up your /boot/grub/grub.conf if you want.

uname -r

to make sure you are running under right kernel.

Then remove your old kernel by running something like

yum remove kernel-2.6.18-xxxxxx

That worked for me, I hope it works for you!

Re: 64bit GoAutoDial

PostPosted: Sat Sep 08, 2012 1:59 pm
by bryan.kewl
I followed the instruction, but the system don't have ztdummy or dahdi_dummy?

any ideas how to get the ztdummy or dahdi_dummy ?

Re: 64bit GoAutoDial

PostPosted: Sat Sep 08, 2012 2:52 pm
by chrisdbarnett
Have you tried running the install again after removing the kernel that was too new?

Re: 64bit GoAutoDial

PostPosted: Sun Sep 09, 2012 6:54 pm
by bryan.kewl
yes, i removed the new kernel and it started working...
I just updated the kernel and had to compile dahdi and install some other packages to make it work with kernel 2.6.18-308.13.1.el5.

lastly I wanted to upgrade PHP 5.1 to 5.3 but failed because of the conflict between php modules and php53 modules. uninstalling php was not possible because "vicidial vtigercrm goautodial-ce goautodial-ce-config phpmyadmin" depends on php. After spending sometime thinking I removed the php which removed "vicidial vtigercrm goautodial-ce goautodial-ce-config phpmyadmin". I checked the /var/www/html/ directory and found that all the apps are still there. I thn installed php53 and all php sub modules like gd, mysql, cli, devel, mbstring etc and now everything is working fine. Will do more testing tomorrow and post results.


EDIT: As now we have php53 in almost all the repos, so can someone replace the dependency from php, php-common, etc to php53 in the goautodial repo?

Re: 64bit GoAutoDial

PostPosted: Wed Feb 20, 2013 2:33 am
by chinita17
hi gardo,

i have an issue with the gouatodial 64bit. The dahdi module is missing everytime i do this process:

4. Install Asterisk and Dahdi packages
yum install asterisk asterisk-perl dahdi-linux kmod-dahdi-linux \
asterisk-sounds-core-en-alaw asterisk-sounds-core-en-gsm asterisk-sounds-core-en-ulaw \
asterisk-sounds-extra-en-alaw asterisk-sounds-extra-en-gsm asterisk-sounds-extra-en-ulaw

and got this warning:

Running Transaction
Installing : libtonezone 1/16
Installing : speex 2/16
Installing : gsm 3/16
Installing : libpri 4/16
Installing : yum-kmod 5/16
Installing : kernel 6/16
WARNING: No module xenblk found for kernel 2.6.18-348.1.1.el5.go, continuing anyway
WARNING: No module xenblk found for kernel 2.6.18-348.1.1.el5.go, continuing anyway
WARNING: No module xenblk found for kernel 2.6.18-348.1.1.el5.go, continuing anyway
Installing : kmod-dahdi-linux 7/16
Installing : dahdi-linux 8/16
Installing : asterisk 9/16
Installing : asterisk-sounds-extra-en-gsm 10/16
Installing : asterisk-sounds-extra-en-ulaw 11/16
Installing : asterisk-sounds-core-en-gsm 12/16
Installing : asterisk-sounds-core-en-alaw 13/16
Installing : asterisk-sounds-core-en-ulaw 14/16
Installing : asterisk-sounds-extra-en-alaw 15/16
Installing : asterisk-perl 16/16

Installed:
asterisk.x86_64 0:1.4.39.1-vici.go
asterisk-perl.x86_64 0:0.08-1.go
asterisk-sounds-core-en-alaw.noarch 0:1.4.21-1_centos5
asterisk-sounds-core-en-gsm.noarch 0:1.4.21-1_centos5
asterisk-sounds-core-en-ulaw.noarch 0:1.4.21-1_centos5
asterisk-sounds-extra-en-alaw.noarch 0:1.4.11-1_centos5
asterisk-sounds-extra-en-gsm.noarch 0:1.4.11-1_centos5
asterisk-sounds-extra-en-ulaw.noarch 0:1.4.11-1_centos5
dahdi-linux.x86_64 0:2.6.1-1_centos5
kmod-dahdi-linux.x86_64 0:2.6.1-1_centos5.2.6.18_348.1.1.el5.go

Dependency Installed:
gsm.x86_64 0:1.0.13-1.el5.rf kernel.x86_64 0:2.6.18-348.1.1.el5.go
libpri.x86_64 0:1.4.11.5-1_centos5 libtonezone.x86_64 0:2.5.0.1-1_centos5
speex.x86_64 0:1.0.5-4.el5_1.1 yum-kmod.noarch 0:1.1.16-21.el5

then when i completely installed the goautodial and try to test it.

"that's not a valid conference number. please try again."

thats what i got. when i lsmod dahdi, no one on the module is working.

what should i do? 1st time happen to me.

Re: 64bit GoAutoDial

PostPosted: Wed Feb 20, 2013 2:45 am
by chinita17
this is the cli:

[2013-02-20 15:44:12] -- Executing [8600051@default:1] MeetMe("SIP/8001-00000000", "8600051|F") in new stack
[2013-02-20 15:44:12] == Parsing '/etc/asterisk/meetme.conf': [2013-02-20 15:44:12] Found
[2013-02-20 15:44:12] == Parsing '/etc/asterisk/meetme-vicidial.conf': [2013-02-20 15:44:12] Found
[2013-02-20 15:44:12] WARNING[10557]: app_meetme.c:829 build_conf: Unable to open DAHDI pseudo device
[2013-02-20 15:44:12] -- <SIP/8001-00000000> Playing 'conf-invalid' (language 'en')
[2013-02-20 15:44:14] == Manager 'sendcron' logged off from 127.0.0.1
[2013-02-20 15:44:16] == Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/8001-00000000'
[2013-02-20 15:44:16] -- Executing [h@default:1] DeadAGI("SIP/8001-00000000", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[2013-02-20 15:44:16] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[2013-02-20 15:44:27] == Parsing '/etc/asterisk/manager.conf': [2013-02-20 15:44:27] Found
[2013-02-20 15:44:27] == Manager 'sendcron' logged on from 127.0.0.1
[2013-02-20 15:44:27] == Parsing '/etc/asterisk/manager.conf': [2013-02-20 15:44:27] Found
[2013-02-20 15:44:27] == Manager 'sendcron' logged on from 127.0.0.1
[2013-02-20 15:44:27] -- Executing [55558600051@default:1] MeetMeAdmin("Local/55558600051@default-addc,2", "8600051|K") in new stack
[2013-02-20 15:44:27] WARNING[10608]: app_meetme.c:3134 admin_exec: Conference number '8600051' not found!
[2013-02-20 15:44:27] -- Executing [55558600051@default:2] Hangup("Local/55558600051@default-addc,2", "") in new stack
[2013-02-20 15:44:27] == Spawn extension (default, 55558600051, 2) exited non-zero on 'Local/55558600051@default-addc,2'
[2013-02-20 15:44:27] -- Executing [h@default:1] DeadAGI("Local/55558600051@default-addc,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[2013-02-20 15:44:27] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[2013-02-20 15:44:29] == Manager 'sendcron' logged off from 127.0.0.1
[2013-02-20 15:44:29] == Manager 'sendcron' logged off from 127.0.0.1

Re: 64bit GoAutoDial

PostPosted: Wed Feb 20, 2013 11:56 am
by williamconley
is this server virtual? what kernel are you trying to install on? Please do post a link to the instruction set you are using (I'm sure Gardo knows where it is ... but what if you were using an old version or some other unexpected concept ... specify your instruction set, and even the line number or section you are on to be sure Gardo knows precisely what you are doing, so he can help!)

Re: 64bit GoAutoDial

PostPosted: Thu Feb 21, 2013 10:37 am
by chinita17
hi william,

no, i tried it on virtual, cloudlinux, centos 5.6, 5.7, 5.9 and 6 version... none of them successfully configure the dahdi module for the goautodial. i tried to recompile the dahdi but i failed to do so because it always looking for the dahdi linux 2.6.18-348.1.1.el5. I tried to downgrade the kernel still unsuccessful wherein i just used the goautodial 64bit just last year in one of my client. weird...

Gardo, I need you power and help.... Please down from the heaven for the meantime.... hehehe! :) your angel's need you so badly... :)

Re: 64bit GoAutoDial

PostPosted: Thu Feb 21, 2013 5:24 pm
by williamconley
It seems to be looking for "xenblk" which I read as an indication that you are in a xen system ... which is virtual?

Re: 64bit GoAutoDial

PostPosted: Thu Feb 21, 2013 10:17 pm
by gardo
We have recently upgraded our RPM repo. It's now based on the latest CentOS 5.X series (which is 5.9). Can you check what kernels are installed on your system? The DAHDI modules were compiled for a specific kernel version. You may have updated your system and need to use the kernel version that DAHDI was compiled for.

Re: 64bit GoAutoDial

PostPosted: Tue Feb 26, 2013 12:51 am
by chinita17
Kernel Version 2.6.18-348.el5xen (SMP)
Distro Name CentOS release 5.9 (Final)

no update happen on the system...

Re: 64bit GoAutoDial

PostPosted: Tue Feb 26, 2013 11:22 pm
by gardo
Looks like you're using a different kernel meant for Xen enabled systems. Are you using GoAutoDial on a virtual machine (as guest VM)?

Re: 64bit GoAutoDial

PostPosted: Wed Feb 27, 2013 11:57 am
by williamconley
williamconley wrote:It seems to be looking for "xenblk" which I read as an indication that you are in a xen system ... which is virtual?
Because of course, the dahdi drivers are not configured for the xen kernel in question. And if I recall, it may not be able to.

Re: 64bit GoAutoDial

PostPosted: Fri Mar 15, 2013 7:03 pm
by gardo
We'll have some updates pretty soon for the 64bit version. We've included DKMS (dynamic kernel module support) so that DAHDI modules get automatically recompiled to whatever kernel version the system is running. No more manual compiling from source.