similar to: Timing source on SMP system - Disable RTCforzaprtc

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: ***

I need a timing device for the DL360G2 for conferencing and meetme. For a timing device I have 2 X100P cards but neither will work in my DL360G2. The system will not even boot with either card in the system. Other PCI cards seems to work fine. I called Digium support and was told that there must be a conflict between the card and my Compaq DL360G2. I then moved on to ztdummy. I'm sure the

Kristian, I have 2 X100P cards but neither work on my Compaq DL360 G2. The system will not even boot! Take a look at my initial post and let me know if you have any other advice. Regardless, thanks for your post! ------------------------------------------------------------------------ - I need a timing device for the DL360G2 for conferencing and meetme. For a timing device I have 2 X100P cards

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

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

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

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

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

What is the most efficient way to allow inbound callers to dial internal users yet restrict them from outbound PSTN calls? Today I have a basic greeting that after a welcome message allows inbound callers the ability to dial any of my users. However, it seems that since I transfer the inbound caller to a context that allows them the ability to call my internal users they have the same rights as

Yes, I tried adding an adaptec that I thought was uhci. This didn't work. I didn't check the specs but figured that they would be uhci given the history of ohci. Regardless, I will confirm with adaptec. Thanks, Chad -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Kristian Kielhofner Sent: Sunday,

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, i am testing stuff for a couple of days now with Asterisk CVS-v1-0-07 and everything worked fine sofar when suddenly the voicemail and musiconhold sound output stopped working. The voicemailmenu still works though. I can see the voiceprompts etc in the debug messages on the asterisk CLI but i cant hear anything. Everything else works fine though. I can call out fine etc. I did some network

This is not directly * related, but could be. My company is using a VoIP conferencing solution that is suffering from developer neglect. I've considered trying to leverage *, and our internal developers can build the management interfaces. If that plan is not accepted by management, I need to find a commercial solution that works. Requirements: H.323 SIP G7.11/G7.29 Multiple unique

I'm testing * (CVS-09/16/03-02:07:49 with zaprtc 0.0.1) with Fritz!PCI (chan_capi 0.3.0), and have a couple of funny things - I wonder if anyone else has seen them: - Now and then, * just exits. Until now I had lowish-level verbosity on, so all I saw was 'Executing last minute cleanups'. What can trigger * exits? (in other words, what should I pay attention to when attempting to

Hi there, since I found a couple of reports with complaints concerning zaprtc I thought that one or the other user might be glad to know that it works indeed. All that was necessary was to copy all *.h files from /zaptel into /zaptelrtc and then do "make" followed by "make load". Of course you'll need to make sure to not have rtc compiled into your kernel, or loaded

Hi, I'm trying to setup a small BRI ISDN <-> voip gateway. The ISDN card is based on Cologne chipset, so I try set it up with zaphfc. The versions i'm running: kernel-2.4.27 Asterisk 1.0.7-BRIstuffed-0.2.0-RC8e zaptel modules 1.0.7 zaphfc is from bristuff-0.2.0-RC8e When I'm doing the insmod on zaptel, zaphfc, zaprtc: Zapata Telephony Interface Registered on major 196 PCI:

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