similar to: CentOS 4.1 x86_64 compiler segfaults

Hi, For a significant time now (since about 0.2.0-rc8n) the qozap driver has become very verbose if an ISDN line is not connected... I get the messages below every couple of seconds in the asterisk logs. The "flaw" in the messages is the "Alarm cleared" message - The alarm cannot possibly be cleared because there is no physical media connected into that port!!! (BTW - All

BUG/SYMPTOMS: 1.Under certain circumstances, octoBRI (and most likely quadBRI) ISDN cards (Junghanns/CologneChip) severely distort certain ISDN payload. 2.Although these claims relate to the bristuff patch, the problem might not be limited to bristuff and in fact be rather asterisk/zaptel/libpri related. 3.Signal distortion is limited to the use of the CVS version of the Bristuff patch for

Hi, I have a couple of questions about Quad-BRI solutions for Asterisk, and was hoping that I might get some feedback based on other people's experience. We currently use the Junghanns card, which is a pure Zaptel solution, which is fantastic, but they have no hardware EC solution, and their drivers are becoming increasingly un-stable with time (I back-port to a modified qozap driver from

Hi list! On a newly installed RHEL 4 box I'm trying to install bristuff-0.2.0-RC8n. Everything did compile but I am running into some problems with the zaphfc driver. First of all when I load zaphfc *before* zaptel (yes I know I shouldn't do that) I get a kernel panic and the box hangs. Not so nice, especially when you are trying to fix stuff from remote locations. But ok. Now for

Hi there, I am attempting to set up a simple BRI and SIP based platform using * with the quadbri card (it's not sharing an IRQ). I enclose my zaptel and zapata.conf files. For the inital test I'm simply trying to connect to the * demo menu. The drivers compile (with a few warning that I believe aren't important - see attachments). chan_zap comiles with the warning: chan_zap.c:

Hello, I am trying to install the drivers for the Junghanns quadBRI card, but am having a problem. I have essentially followed the procedure from http://www.voip-manager.net/installation-linux-asterisk.php. At the stage to install the ISDN card I have completed the following: 1) downloaded the bristuff-0.2.0-RC8q.tar.gz to /usr/src 2) unpacked it in /usr/src - tar xvzf bristuff-0.2.0-RC8q.tar.gz

Hi, I had problems described in another thread so went from a start, but now have problems when loading qozap module. I get : # insmod qozap.ko ports=9 insmod: error inserting 'qozap.ko': -1 Unknown symbol in module and in /var/log/messages: module qozap unsupported by SUSE/Novell, tainting kernel. qozap: disagrees about version of symbol zt_receive qozap: Unknown symbol zt_receive

Hi all, I am currently planning a new home file server on a gigabit network that will be utilizing ZFS (on SXDE). The files will be shared via samba as I have a mixed OS environment. The controller card I will be using is the SuperMicro SAT2-MV8 133MHz PCI-X card. I have two options for CPUs/motherboards: AMD Athlon64 3000+ (64 bit) DFI LanParty UT 250gb (NForce 3 based) motherboard 32 bit

Hi, we are trying to install Junghann's quadBRI into Dell PowerEdge 2800 system without success. I don't know if the issue can be that Junghann's card fits 32-bit slot and Dell PE 2800 has only 3 PCI-X 64-bit slots. Can this be an issue? We get "CRC errors for HDLC frame" when the card is initialized. Any idea what can be wrong? 1/ We use latest bristuff packages. 2/

Hi, I'm trying to connect quadbri between powered ISDN phone and ISDN line: ISDN <---1---> TE - * - NT <--2--> Phone I use quadbri, suse 9.2 and latest 0.2.0-RC7k bristuff. I've used sample settings provided with package, but do get strange error (I think that I have wrong setting for P2P or P2MP setting and cables 1 and 2). If I connect phone to ISDN with straight cable

Hi, (cc. asterisk-users, hope that is not a big Faux Pas) I've had trouble with the qozap driver for a LONG time now, where it will not recognise and ignore a missing ISDN2 line on a quad card if one of the 4 ports is unplugged or somehow faulty. The symptom is that is correctly recognises the fault, but then clears the RED ALARM almost immediately, leaving Asterisk thinking that it can call

Hi, We installed the latest 1.4.24 on a test machine and can't get zaptel nor dahdi compile. It's a Linux Debian Etch. Errors we have: keewi:/usr/src/dahdi-linux-2.1.0.4# make make -C /lib/modules/2.6.18-custom.2/build ARCH=i386 SUBDIRS=/usr/src/dahdi-linux-2.1.0.4/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-2.1.0.4/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes

- I'm not a Linux user i'm trying to get in it ... - Fedora core 1 - QuadBRI card bought from junghanns.net - We want to use the card in TE mode to connect to the TELCO - Downloaded BRISTUFF0.0.2(stable) latest from junghanss.net/asterisk - followed the instructions on voip-info.org - compiled everything still got the error when "make load" in qozap : insmod ./qozap.o

Hi All I have a Junghanns BRI 4 port installed where only the first channel of each line is working i.e. channels 1 and 4 work but 2 and 5 don't. Our config is the same on this box as 15 other similar installations where all works well. the only error I see is in /var/log/messages: Jun 28 15:49:31 pbxct kernel: qozap: CRC error for HDLC frame on card 1 (cardID 0) S/T port 2 Jun 28 15:51:27

Good day all Is there a fix for these errors yet for the junghanns cards Jul 26 17:15:05 pbx1 kernel: qozap: dropped audio card 1 cardid 0 bytes 6 z1 1 z2 107 Jul 26 17:15:18 pbx1 kernel: qozap: dropped audio card 1 cardid 0 bytes 6 z1 10 z2 116 Jul 26 17:15:18 pbx1 kernel: qozap: dropped audio card 1 cardid 0 bytes 5 z1 118 z2 97 Jul 26 17:16:33 pbx1 kernel: qozap: dropped audio card 1 cardid

Hi all, Using Asterisk 1.0.10-BRIstuffed-0.2.0-RC8q with a Junghanns quadBRI (2 spans connected) and a Digium TDM400 for extensions Shouuld I be worried about these lines that keep showing up in my /var/log/messages? qozap: dropped audio card 1 cardid 0 bytes 6 z1 10 z2 116 qozap: dropped audio card 1 cardid 0 bytes 6 z1 50 z2 28 qozap: dropped audio card 1 cardid 0 bytes 6 z1 59 z2 37 .. ....

Hi all, I'm trying to get a junghanns QuadBRI to coexist in the same machine as a Digium TDM400P card (so I can run the ISDN lines in and bridge with analog phones plugged into the TDM). I'm having a problem loading the modules. If I follow the BRIstuff (0.3.0-pre-1l) install method.... it's to modprobe zaptel, then insmod qozap.o I'm on Debian 2.4.31. That works. But then I

Hello I am using a Junghanns QuadBRI ISDN card - the module name is qozap. If I like at my interrupt assignment, qozap is sharing interrupt 10 with libata and uhci_hcd. I think libata is the IDE hard drive module and uhci_hcd is a USB module. linux:~ # modprobe qozap linux:~ # cat /proc/interrupts CPU0 0: 12634579 XT-PIC timer 1: 10 XT-PIC i8042

Hi, it helps to have configured and working kernel sources installed. Configure your kernel sources for the running kernel and then run "make" in the kernel source dir to build the necessary scripts. You dont have to wait until the kernel is compiled. best regards Klaus -- Klaus-Peter Junghanns Am Samstag, den 25.06.2005, 02:45 +0200 schrieb Stefan Gofferje: > Hi folks, > >

If the linux kernel was built using O=builddir, there is no correct choice for the linux symlink in klibc-1.5. See below for the possible outcomes: ----------------------- KLIBCCC usr/klibc/vsnprintf.o In file included from usr/include/sys/types.h:15, from usr/include/unistd.h:11, from usr/include/stdio.h:11, from usr/klibc/vsnprintf.c:13: