similar to: qozap drops -- possible to bridge BRIstuff ISDN to analog zaptel phone?

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, 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 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, 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 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

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, 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, (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, I'm trying to install a Junghanns quadbri for a few days but i stay with an asterisk error. (Everyone is busy/congested ) Asterisk is working with a Fritz PCbut from one year and now i want to add the quadbri. The quadbri card has been configured in NT mode and with no 100 ohms S/T termoination. (I'm not sure if the S/T parameter is correct) I have installed the bristuff package

Hi, I have installed a quadBri card, with Asterisk-1.0.10 and the bristuff-0.2.0-RC8s (* 1.0.10) When calling 0207654321 the following happens: -- Executing Goto("Zap/1-1 ", " salsa-helpdesk-day|s|1 ") in new stack -- Goto (salsa-helpdesk-day,s,1) -- Executing Dial ("Zap/1-1 ", "Zap/g1/0201234567|30 ") in new stack -- Requested transfer capability:

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

Hi everyone. We have a problem here... Hope somebody can give us some hints. We have a HP ProLiant DL180 G6 Server with a Debian/Lenny sytem. Asterisk 1.4.21.2 (1.4.21.2~dfsg-3+lenny1) with zaptel (1.4.11) and libpri (1.4.3) is installed. There is a QuadBRI-Card installed: # lspci -vv -s 06:04.0 06:04.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)

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:

I am unable to make quadbri board to work in NT mode, in TE mode it works OK. I have set 5 jumpers to NT mode. Dmesg shows everything OK: qozap: Junghanns.NET quadBRI card configured at mem 0xd084e000 IRQ 9 HZ 100 CardID 1 qozap: S/T ports: 4 [ TE TE TE NT ] qozap: 1 multiBRI card(s) in this box, 4 BRI ports total. from Asterisk side seems to be ok. pri show span 4 Primary D-channel: 12 Status:

Hi all, is it possible to bridge a call between a Junghanns quadBRI card and a TDM400 in the same server? It should be I think, -- I am trying this and when an incoming call comes in, it hangs both up at the moment the bridge is attempted (and a subsequent 'qozap: dropped audio' error is show in the /var/log/messages) Any thoughts appreciated -- I've seen posts, but no clear

On Friday, March 31, 2006 3:52 PM Chris Earle wrote: > I'm wondering if I should be using zapHFC with my Junghanns card > instead of qozap? Why would you want to do that? Sorry if I missed the start of the problem but qozap is what you want to use with your Junghanns card (at least if you want to stay with zaptel/libpri). > Everyone always mentions zaphfc -- mostly I >

Hello, I have about 10 Asterisk PBX in production with Bristuff-0.2.0-RC8q (asterisk 1.0.10) and I want to use Bristuff-0.3 now for the new PBX I am going to set up. With Bristuff-0.2.0-RC8q the ISDN lines are working fine, but the new version of Asterisk add some nice features. All these PBX are in France with France Telecom lines. When I use the new version after about an hour with

Hi, In my 1.6.1.18 with dahdi 2.2.1.1, I've got : # dahdi_hardware pci:0000:01:0a.0 qozap- 1397:16b8 Junghanns OctoBRI ISDN card Does it mean I should download and use qozap or is it a bug in Dahdi ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100412/de87e46e/attachment.htm

Does anyone test Asterisk 1.2.X + bristuff-0.3.X and TDM card? We can't get it to work. -David -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Julian J. M. Sent: Friday, March 31, 2006 1:44 AM To: Chris Earle; Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Re: BRI

Hello, ? I have a Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] card which seems to work on 1 machine but not on another. It SHOULD load this driver: ? >dahdi_hardware -v pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card Instead of: >dahdi_hardware -v pci:0000:00:00.0 qozap- 1397:08b4 Generic Cologne ISDN card There is no qozap modul in