similar to: my hfc card does not like Siemens

Hello, I am trying to use a HFC-PCI (CCD/Billion/Asuscom 2BD0) card in TE mode to dial-in and out with ISDN. The problem is I can not get the card to dial out with a Zap channel. Dial-in is working. I am using bri-stuff 0.1.0-RC4 (but tried also RC3 and RC2k). I tried all combination of "immediate", "overlapdial", "pridialplan". I earlier also managed to dial out

Hi list, Now that I've got my Asterisk server to recognize my HFC-PCI card, I've run into some serious problems. The first thing I noticed was this message that would show up every five seconds on the CLI: Dec 27 15:46:42 WARNING[12484]: chan_zap.c:2512 pri_find_dchan: No D-channels available! Using Primary channel 3 as D-channel anyway! == Primary D-Channel on span 1 down

Hi list, After upgrading from Asterisk v1.2 to v1.4.14, all kinds Zaptel error messages related to my HFC-S PCI card disappeared, but now I can't access the card's resources because it always seems to be busy. Any idea why? Thanks, Jaap PS -- Below is some info regarding my configuration. =========================== Zaptel version: 1.4.7 (incl. firmware and modules). OS: Debian

Hello everybody, I'm having little trouble (well, pretty big trouble) with HFC-S card and Asterisk. My idea is to do VoIP/IAX link between two HW PBXen using two Asterisk PC boxen with ISDN cards in them. AFAIK HFC-S cards must be in NT mode for this installation, they must behave like state line for those HW PBXen. (if wrong, please correct me). Diagram follows:

Hi list, Attempting to get an ISDN-BRI line connected using an HFC-S PCI card together with Asterisk v1.4.14 and Zaptel 1.4.7 on a Debian etch system, I find that I can't access the card's resources because the channels are always be busy. An attempt to call out results in the following CLI output: == Primary D-Channel on span 1 down == Primary D-Channel on span 2 down

Hello, I have asterisk@home with zaphfc patch applied (http://dondisperato.blogspot.com/), but I can not make call to legacy PBX (Alcatel 4400). I can only accept incoming calls. I am dialing with this: exten => 202,1,Dial(Zap/g1/242) --- asterisk1*CLI> bri debug span 1 Enabled debugging on span 1 -- Executing Dial("SIP/201-4678", "Zap/g1/242") in new stack

Hi Folks, I've Asterisk Bristuffed up and running behind an Auerswald Commander Basic ISDN PBX on the internal ISDN Bus (BRI/PTMP). The HFC Card works marvelleous for outgoing calls (as the parallely installed avm fritzcard with chan_capi does), but when I'm trying to call in, I get a short ring signal and then the connection is terminated. This does not happen with chan_capi and

Hello, The harddisk of my etch/bristuffed asterisk1.2 box finally died. I moved the cheap (1397:2bd0) HFC-S card to a squeeze host (i686) and built dahdi modules 2.3.0.1 using m-a. After zaptel->dahdi and asterisk 1.2->1.6 config adaptations, everything seems ok, except for the BRI side, unable to bring layers 1/2 up. Asterisk reports: chan_dahdi.c:12393 dahdi_pri_error: 1 Unable to

Salve, I'm somewhat stuck on how to get DTMF working with my setup and googling didn't yield anything similar. My setup consists of one CAPI-capable board (AVM Fritz!DSL) connected to a BRI (T-ISDN), one HFC-S board running in NT-mode connected to an internal S0 bus with some ISDN devices (DECT stations, TA) and, of course, some ethernet interfaces. ISDN standard used is Euro-ISDN.

Hi, I've set up an Asterisk as voip gatway: VOIP <-> Asterisk <-> hfc-s card <-> NTBA <-> Siemens Gigaset Dect ISDN pbx. Outgoing calls from dect handset to the world are working. Incoming calls don't even ring the handset. I'm using the dahdi driver with the zaphfc kernel module. The hfc-s card is in nt mode. The msn is set at the dect phone/base station

Hi, I have debian etch 4.0 machine (2.6.18) with two TW-ISDN PCI (Hfc) cards. I use bristuff-0.3.0-PRE-1y-e (asterisk-1.2.17,libpri-1.2.4,zaptel-1.2.16). I also have patched zaphfc with zaphfc_0.4.0-test1_florz-13.diff.gz (I load module: insmod /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko modes=1 debug=1). So i want to test two cards and make loop between them. So one card would be NT,

Hi all, I tried to connect the bristuffed(0.3.0-PRE-1i) * to an Alcatel PBX via BRI (zaphfc) and Q.SIG. The Alcatel PBX is connected to the outside world and should forward our calls to the telco. This setup works correctly as far as I use euroisdn as the switchtype. The first problem was that it is only possible to run the * side in CPE-mode -- I wanted NET. Anyway, I configured * this way:

Hello * users I've problems with sound quality on zaphfc Asterisk works fine good sound quality. If I do "make load" in the bristuf.xx zaphfc dir then sound quality drops directly. Even if I don't load the chan_zap in the modules.conf I use this config on more (even old 400Mhz machines) and works correctly. Looks like an hardware problem but I can't find it. I don't

Hi All ... I'm running Asterisk 1.2.13-BRIstuffed-0.3.0-PRE-1v which has a Junghanns QuadBri card in it (lspci reports Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)) I have a regular KPN ISDN2 Line connected which works fine with the the zapata.conf below. However, I also have a new KPN ISDN Mutli (meervoudig) line (PBAX-Group), which works fine for incoming calls,

Hi, It's the first time i try to configure an ISDN card with dahdi, so my experience is very poor (be kind ;)) My problem is with dahdi_genconf, when i start it it says: /usr/sbin/dahdi_span_assignments: Missing '/sys/bus/dahdi_devices/devices' (DAHDI driver unloaded?) Command failed (status=256): 'dahdi_span_assignments dumpconfig > /etc/dahdi/assigned-spans.conf' at

Hi, When we make an outgoing call on ISDN (zaphfc) with overlap dialing we get immidiate hangup after answer. But when we place a full number before dialing everything is ok. Any help appriciated!! Thanks here is info with debug: == Primary D-Channel on span 1 up -- Executing Dial("SIP/200-164c", "zap/g1/|100|tc") in new stack -- Making new call for cr 192 --

Hello, After searching the archives, I''ve found only two messages regarding this case, but there were no solution. I have a similar problem, so I try to ask here. I have twi HFC chipset ISDN cards in my pc: 0000:00:0d.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02) Subsystem: Cologne Chip Designs GmbH ISDN Board Flags: bus

Hi! I just wanted to ask if anyone managed to get "ordinary" HFC-S ISDN cards with the zaphfc driver running in a Xen3 DomU. I am referring to this post ( http://lists.xensource.com/archives/html/xen-users/2007-04/msg00202.html ), which perfectly describes my problem and I am therefore going to simply copy-and-paste it here: ----------- snip ------------> Hi, I''m

Hi All, what is this? This happens after calling "make loadNT" And I can't do anything with this HFC Card, but the installscript from bri-stuff finished successfully! Aug 17 02:31:42 server kernel: zaphfc: freed one card. Aug 17 02:33:27 server kernel: PCI: Enabling device 00:12.0 (0000 -> 0003) Aug 17 02:33:27 server kernel: PCI: Found IRQ 10 for device 00:12.0 Aug 17 02:33:27

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 >