similar to: zaprtc on Debian Sarge 2.4.27

I finally got 2.4 recompiled with RTC as a module: Module Size Used by Not tainted autofs 13684 0 (autoclean) (unused) acenic 241092 0 (unused) iptable_filter 2412 0 (autoclean) (unused) ip_tables 15864 1 [iptable_filter] e100 62340 1 rtc 9084 0 (autoclean) Here is my

zaprtc 'load' is failing on my machine (the make was fine, same output as other posts to this list) [xxx@xxx zaptelrtc]# make load sync modprobe zaptel insmod ./zaprtc.o ./zaprtc.o: init_module: Input/output error Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or

Hullo. Having found http://bugs.digium.com/bug_view_page.php?bug_id=0000875 I grabbed the original 0.0.1 and Dan's patch, and whilst it didn't apply, I was able to patch the zaprtc.c manually - the Makefile has changed a lot, and I wasn't able to understand the changes. (this is all on a machine that's never had any * on it before, and has a 2.6.5 kernel with a matching

Hi, I don't have a zaptel device for conferencing. I read from the lists, that ztdummy and zaprtc need to be installed to get conferencing. I could able to compile successfully with ztdummy and when i receive the call it says, -- Goto (13732,s,1) -- Executing MeetMe("SIP/-08118800", "1234") in new stack == Parsing

Has anyone successfully compiled zaprtc on Debian Sarge using the 2.4.27 kernel. I have a symbolic link from linux-2.4 to linux. I compiled a new kernel from source and have been able to compile zaptel as well. The main error seems to be: /usr/include/asm/mpspec.h:6:25: mach_mpspec.h: No such file or directory These are the errors that I am getting: cc -c zaprtc.c -D__KERNEL__ -DMODULE

Does anyone know where to disable rtc support on redhat 9.0 using make menuconfig? I thought I disabled it but still got the following error when trying to make zaprtc: zaprtc.c:109: storage size of `rtc_irq_timer' isn't known zaprtc.c:719: storage size of `rtc_fops' isn't known zaprtc.c:107: warning: `DECLARE_WAIT_QUEUE_HEAD' declared `static' but never defined make: ***

Hello, i would like to use Meetme and i need zaptelrtc for that, since i dont have any USB devices or a card from digium. I compiled it on Llinux 2.6.8 and all i got was a zaprtc.o which obviously wont work with a 2.6 kernel: ~/zaptelrtc# make load sync modprobe zaptel insmod ./zaprtc.o insmod: error inserting './zaprtc.o': -1 Invalid module format make: *** [load] Error 1 Is there a

I feel there is some unclarity about the need for a timer in Asterisk. As Asterisk moves into production environments, this needs to be sorted out. I'm setting up an Asterisk in a production environment with no Digium cards at all. It is planned to be used as a clean SIP hosted PABX, where we connect to the PSTN via gateways with proper echo cancellation. There is no USB driver on the card.

Hi, I'm trying to intall zaprtc on my machine (I don't have UHCI_USB nor Zaptel) and I have a strange behaviour during loading. When I do >make load I have : ./zaprtc.o: init_module: Input/ouput error With a quick dmesg got: rtc: I/O port 112 in not free Is someone have any idea to solve this ? I saw on the README file that rtc support should not be enabled in the kernel, but I

I have compiled the zaptel library and zaprtc on a system that gives the following from "uname -a": Linux fxxxxxx76.mydomain.de 2.4.18-64GB-SMP #1 SMP Wed Mar 27 13:58:12 UTC 2002 i686 unknown Makefile for zaptel had the following line uncommented: # KFLAGS+=-D__SMP__ When doing the "make load" for zaprtc I get the following error: modprobe zaptel

I have a system with no Digium hardware in it (two others with 2 X100P cards in each of them as well). I'm interested in using MeetMe in the one without the hardware (it works great in the ones with the hardware). I can't use ztdummy, because the system has usb-ohci drivers, rather than usb-uhci. I have read the little there is about zaprtc, and I am wondering whether there is a

I am still stuck, anyone got any ideas ? Hi, Having no digium hardware in my box and two cpus and a ohci usb bus im forced to use zaprtc. I have recompiled the kernel and removed enhanced rtc support. When I attempt to compile zaprtc I get the following error. zaprtc.c:1077: warning: implicit declaration of function `barrier' zaprtc.c:1078: warning: implicit declaration of function

I'm having a similar issue to this in that the USB ports on the system are ohci based, not uhci, therefore ztdummy will not work. My system is also running the SMP kernel so zaprtc will not work. To me it looks like the only good solution is a hardware timer, even if it's as simple as an x100p card. Kelly PS. If you read Jon's message again, the answer given is not acceptable for

I'm trying to take advice to use "zaprtc from bristuff" (from both a posting here and references on voip-info) because I have a 2.4 kernel SMP machine. I've downloaded and installed bristuff-0.2.0-RC3a and now have the modules zaphfc and zaptel loaded. Running meetme says the extension is invalid (I've double checked meetme.conf and extensions.conf). There is no zaprtc

Any help would be appreciated as I am a novice trying to work around a difficult situation. This is what the zaprtc helpfile says: zaprtc, getting zaptel timing out of your realtime clock ======================================================== Make sure that you _dont_ have rtc support compiled into your kernel! INSTALL: make USE: make load REMOVE: make unload I interpreted this as

I updated Junghanns' zaprtc to work with a 2.6 kernel. It is not extensively tested, but does compile cleanly installs without errors and works with Meetme conferences. Since this code is not part of the zaptel cvs, I'll be happy to share the diff, or if the Bug Marshalls would not mind open a bug and post the diff there. (One caveat, on unload the zaprtc module does not seem to

I've compiled Asterisk on Redhat 9 and Fedora Core 1 in the past, generally without any problems. Especially w/ the stock kernel, which I generally loathe. When I tried to upgrade my Redhat 9 Server to the 2.4.27 kernel, doing a manual/clean compile, I had massive quality issues. I was forced to go back down to a stock 2.4.24 kernel. Never figured out why. Now, I've installed Gentoo

Hi, ztdummy says the following: VoiceBOX:/usr/src/zaptel# modprobe ztdummy /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_register /lib/modules/2.4.18/misc/ztdummy.o: insmod

Hi to everybody, seems that I cannot load the zaptel modules: ztdummy says the following: [root@Hayabusa misc]# modprobe ztdummy /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_register

Hi there, I know this question is kind of stupid. But, I don't know anywhere else to ask. I've received some answers when I asked about the need of having a zaptel interface to make the meetme application work, that said that it was better to have a real hardware then the zaptelrtc software modules. So, my question is, would any of the following cards work with the meetme