Okay,Thanks for that and if you need another system to test on let me know. I have two cards in mine with an intel P3 1.3GHz, intel mainboard and 1.5GB Ram. The system is on a 36GB scsi 160 LVD and the home dir is 5x 70gb scsi sca 160 LVD Raid 5. The only problem is now I have started working on this and have started kinda making my own thing for asterisk (adding features) as well as the zaptel drivers. Are there any diffs available for what you had to change in asterisk or did you just build a wrapper against the current code? Sorry, Debian is not what I'm used to so it will take a bit for me to adjust from Fedora.Regards,Cordel

I need this too (zaptel modules). I decided to try to compile the modules myself, but I am having problems loading them....so I need to investigate more. I too am not familiar with Debian (familiar with SuSE and Fedora).

Has anyone had success loading the drivers, and if so, what steps did you take?

Asterisk has to be compiled with the drivers so not quiet that easy. I have been putting together a list of popular packages/add-ons (weater, wakeup calls, etc..) for asterisk and drivers for the more popular cards. Good to know that your updating to sarge so I can plan for this. I'll get these packaged up and add them to my mantain list and see how it goes.regards,Cordel

Actually in test setup we had, we only compiled zaptel modules and config utility.Asterisk, libpri and so on was left untouched.

Then you just load the needed module, change /etc/zaptel.conf, /etc/asterisk/zapata.conf according to your card configuration, configure asterisk via AMP included in pluto-admin website..and it should work.

I'm not an expert in configuring Digium cards, I done this only once after a lot of googleing but it worked

The reason I ask, is because I am having problems compiling the modules for Debian. I've never had problems compiling them for Fedora and SuSE, but for the life of me, I can't for Debian. Would anyone mind just spelling out exactly what they had to do to get them compiled...including which kernel version, etc?

Compiling kernel modules for Debian is almost same as compiling for any other distribution. However the problem is that Debian (and Pluto) separates kernel from it's headers (configured for that particular kernel).I found that in our repositories we don't have a matching package for our kernel. So I will contact the person which is responsible for building kernels, and hope that in next release we'll have everything you need (actually we plan to include zaptel modules into standard kernel, so you probably won't need to manually compile modules)

This can take some time because right now pluto is upgrading to sarge and a newer kernel.

I managed to make plutohome find my two Zaptel cards, but it wasn't fun

Basically, I insmod'd the /lib/modules/2.6.13-2-vanilla-pluto-1-686/misc/zaptel.ko module, and then the wcfxo module. Now I've got both modules in the kernel, and dmesg show my two cards. It looks like all the modules are there, for the 4 port cards as well.

Modules are there, but setting a zaptel card is not very easy.You have to:- modprobe the drivers- manually edit /etc/zaptel.conf and /etc/asterisk/zapata.conf (I don't remember what to put there, we don't have such card in the office and i only did it once on a remote machine)- launch /sbin/ztcfg(modprobe first the other two not sure in what order)- restart asterisk with "/etc/init.d/asterisk restart"- connect to asterisk with "asterisk -r" and check for zap channels to be correctly recognized- add zap extension in AMP- add zap trunk in AMPI think after that everything should work, and if you add zap trunk and extension in AMP, it will know about it and will not ruin your configuration.