similar to: cat /proc/zaptel/*

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

so here it is, the problem that's been nagging me for the past 2 days: connected a box to my telco's NTBA <-> zap/asterisk. which works: box:/etc/asterisk# cat /proc/zaptel/1 Span 1: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] layer 1 ACTIVATED (F7)" HDB3/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In

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

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, For a while now I've been using Asterisk together with HFC-PCI cards (Cologne chipset) for Euro-ISDN BRI support. However, I do not consider this to be the most reliable solution and believe that the most stubborn problems have always been software related. If my clients are willing to spend a bit more money on different hardware, what do you think the best solution would be?

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

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

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, After wrestling with the voicemail system for a while (Asterisk 1.4.14, Debian etch), I got it to work, but I still have lots of questions, like: * Why can't I delete any voicemail messages? (Response: "Message undeleted.") * Why can't I listen to the messages in the Old folder? * Why can't I use the advanced options? (Response:

Hi folks, My client and I are having a problem getting a portable Esaote ultrasound machine to connect to a Samba server. The unit has an integrated laptop with a Windows XP version that can hardly be modified. Upon delivery the vendor only changed the user name and workgroup for us. When I asked for the user password to make a matching Samba account, the vendor refused because they use

Hi folks, Following an upgrade to Debian wheezy, I'm now running Asterisk 1.8.13.1. As opposed to Asterisk 1.6.2.9 that I ran with squeeze, this version can support IPv6. However, it seems that I can't get it to support both IPv4 and IPv6 at the same time. For example, if in sip.conf I set the bindaddr variable to '::' it will only listen on IPv6 and none of my IPv4-only

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 folks, Following an upgrade from Debian squeeze to wheezy, and Asterisk 1.6.2.9 to 1.8.13, my server is no longer able to register a connection to a SIP account at my ISP (XS4ALL in the Netherlands). At the same time, it is still able to register a different account with another SIP provider, so it must be that they no longer have the same basic requirements. The relevant part of my

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

Hi list, Can someone please explain how to get one touch recording (automon) to work reliably? I'm using Asterisk 1.4.14 on a Debian etch system. My current configuration includes the following settings: In /etc/asterisk/sip.conf: [2000] ; Siemens Gigaset S675 IP wireless SIP phone. type=friend secret=1234 context=phones-j dtmfmode=rfc2833 qualify=yes