similar to: Problems with zaptel and HFC-S PCI card

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

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

Hi list, Has anyone been able to get ISDN-BRI support to work reliably on Asterisk 1.4? If so, I'd love to know how you did it (hardware, distro, kernel, modules, versions, config files). I've tried to get it to work on a Debian etch system with an HFC-PCI card and the zaptel package (v1.4.7, also from xorcom.com), but with no luck: all three channels that are created when the

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:

Hi all, Previously, I had the PrivacyManager working for me exactly as would be expected, but after upgrading the OS to Debian lenny and Asterisk to v1.4.21.2 that's no longer the case. Anonymous callers are still confronted with the PrivacyManager, but now no matter what I set the minlength value to, e.g.: exten => jaap,n,PrivacyManager(1,1) ... (I'm not using a

Hi, i've downloaded/compiled/installed the bristuffed asterisk Asterisk 1.0.7-BRIstuffed-0.2.0-RC8a and i'm using it with an hfc card. It runs on a debian 3.1 sarge machine with kernel 2.6.11. Asterisk works well if i configure the card using isdn4linux. I'm having problems dialing out (not tried the input yet). This is the output from asterisk: -- Accepting AUTHENTICATED call from

Hi all, On an Asterisk/Zaptel 1.4 system, one way to gather diagnostic info is: ~# cat /proc/zaptel/* Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In use) Span 2: ZTHFC2 "HFC-S PCI A Zaptel Driver card 1 [TE]" AMI/CCS 4 ZTHFC2/0/1 Clear 5 ZTHFC2/0/2

Hi list, Before purchasing a number of Siemens DECT SIP phones, the Gigaset S675 IP, I read that the problems with MWI had been fixed with the latest firmware version (see http://www.voip-info.org/wiki/view/Siemens+Gigaset+S675IP). Now I'm not so sure that's the case. After setting up a network mailbox for one of these phones, as well as an Asterisk voicemail account (ext.

Hi list, After a recent upgrade to Asterisk v1.4.14, my message log is now filling up with the following error messages: <-------------> [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645 determine_firstline_parts: Bad request protocol Packet --- (1 headers 0 lines) --- bitis*CLI> <--- SIP read from 82.101.62.99:5060 ---> Cirpack KeepAlive Packet <-------------> Seeing

Hello, I tried to connect my Siemens ISDN 4170 cordless small PBX to the asterisk with an Acer HFC isdn card but I have not seen any success. The asterisk can see the card but no success to receive or dial a call. The Siemens 4170 gives fault in all the handsets with trying to dial and does not receives anything. I have linux kernel 2.4.29, asterisk CVS-v1-0-03/12/05-17, zaphfc

Hi list, After failing to get a Sipura/Linksys SPA3000, which I've configured as a PSTN gateway, to pass on the Caller ID, I decided to try my luck with a Linksys SPA3102 after hearing some promising stories. Unfortunately, I've run into a completely new problem: it seems Asterisk won't let this device register. I went about configuring the SPA3102 in much the same way as I

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,

I have some problems starting asterisk with a hfc card using zaphfc: [chan_zap.so]Mar 8 17:53:06 WARNING[2447]: loader.c:258 ast_load_resource: /usr/lib/asterisk/modules/chan_zap.so: undefined symbol: ast_retrieve_call_to_death Mar 8 17:53:06 WARNING[2447]: loader.c:391 load_modules: Loading module chan_zap.so failed! I'm using asterisk from debian/sid: Asterisk

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:

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

Hi! I'm struggeling had to get a hfc pci card working in NT-Mode. I've installed a very basic test system with just one hfc pci card connected to an ISDN-phone over a modified NTBA as described on jollies homepage. I commpiled asterisk as descibed in kape's INSTALL file that comes with 'bri_stuff'. I have not modified the config fieles yet. After connecting to asterisk by

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

I have the same problem in a box with 2 HFC-PCI, but i already remove the row in modprobe.conf and load the module manually. Both cards works fine Any idea ? Giordano -----Messaggio originale----- Da: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] Per conto di Julian J. M. Inviato: luned? 27 giugno 2005 12.04 A:

Hi All, It's broken !! (drat) Asterisk if failing to load with the following error (taken from end of /var/log/asterisk/full) after adding bristuff. Can anyone help please? Jul 17 19:57:54 VERBOSE[2503]: == Registered channel type 'Phone' (Standard Linux Telephony API Driver) Jul 17 19:57:54 VERBOSE[2503]: [chan_zap.so]Jul 17 19:57:54 VERBOSE[2503]: [chan_zap.so] =>

Hi all, In our asterisk box we have a Fritz card and an HFC card. So far I've had the Fritz card working well, but its time to connect the HFC card up to the ISDN line and get it working. I've followed the instructions on voip-info.org here: http://www.voip-info.org/wiki-Asterisk+zaphfc+install and here: http://www.voip-info.org/wiki-Asterisk+zaphfc+install But when it comes to