similar to: dahdi-linux 2.0.0 and dahdi-tools 2.0.0 released

The Asterisk development team is pleased to announce the release of versions 2.1.0 of both dahdi-linux and dahdi-tools. DAHDI now includes a native driver for the B410P four port BRI module. The Digium Asterisk Hardware Device Interface (DAHDI) is a collection of drivers and utilities for connecting your Asterisk installation to the Public Switched Telephone Network (PSTN). dahdi-linux is the

The Asterisk development team is pleased to announce the release of versions 2.1.0 of both dahdi-linux and dahdi-tools. DAHDI now includes a native driver for the B410P four port BRI module. The Digium Asterisk Hardware Device Interface (DAHDI) is a collection of drivers and utilities for connecting your Asterisk installation to the Public Switched Telephone Network (PSTN). dahdi-linux is the

The Asterisk development team is pleased to announce new releases of Asterisk and DAHDI. For more information on the reasoning behind the transition to DAHDI, please see the following post: http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The list of packages released today includes: dahdi-linux 2.0.0-rc4 dahdi-linux-complete 2.0.0-rc4+2.0.0-rc2 asterisk 1.4.22-rc4

The Asterisk development team is pleased to announce new releases of Asterisk and DAHDI. For more information on the reasoning behind the transition to DAHDI, please see the following post: http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The list of packages released today includes: dahdi-linux 2.0.0-rc4 dahdi-linux-complete 2.0.0-rc4+2.0.0-rc2 asterisk 1.4.22-rc4

The Asterisk development team is pleased to announce new releases of Asterisk, Asterisk-Addons, Zaptel, and for the first time, DAHDI. This is a set of coordinated releases intended to begin the transition from Zaptel to DAHDI; for the reasons why this is being done, please see: http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The list of packages released today

The Asterisk development team is pleased to announce new releases of Asterisk, Asterisk-Addons, Zaptel, and for the first time, DAHDI. This is a set of coordinated releases intended to begin the transition from Zaptel to DAHDI; for the reasons why this is being done, please see: http://blogs.digium.com/2008/05/19/zaptel-project-being-renamed-to-dahdi/ The list of packages released today

The Asterisk Development Team has announced the releases of: DAHDI-Linux 2.6.1 DAHDI-Linux 2.5.1 DAHDI-Tools 2.6.1 DAHDI-Tools 2.5.1 DAHDI-Linux-Complete 2.6.1+2.6.1 DAHDI-Linux-Complete 2.5.1+2.5.1 These releases are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

The Asterisk Development Team has announced the releases of: DAHDI-Linux 2.6.1 DAHDI-Linux 2.5.1 DAHDI-Tools 2.6.1 DAHDI-Tools 2.5.1 DAHDI-Linux-Complete 2.6.1+2.6.1 DAHDI-Linux-Complete 2.5.1+2.5.1 These releases are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems

Not sure how I should officially report this, but I'm getting a compile error with DAHDI-linux 2.7 when I define CONFIG_DAHDI_NET in include/dahdi/dahdi_config.h. I am able to compile successfully when I leave it undefined, but I need to be able to use the network support. <snipped> /oct6100_api/oct6100_tsst.o AR /tmp/dahdi-linux-2.7.0-net/drivers/dahdi/oct612x/lib.a

Looking for some help from the UK please. I backed up all my Asterisk configuration before re-installing the server from 32 -> 64 bit. Unfortunately I did not transfer the backup to another machine!!!!! I now have a TDM400P that is not picking up the line. Can you see what I have done wrong when I have rebuilt the config please: dahdi_scan ---------- [1] active=yes alarms=OK

Hi, I'm using a revision 6822-enabled Dahdi-Tools (see https://issues.asterisk.org/view.php?id=13897) with a Junghanns QuadBRI. 1. Do I still need qozap driver ? If positive, how is it recommended to get it ? 2. Which line should be included in /etc/dahdi/modules to have the appropriate driver loaded ? 3. The process I'm planning to use is : A- Hand edit /etc/dadhi/modules,

Hi, Thanks for giving me a detailed reply on hardware needs steven. I have been looking at the archives in detail and found a few people have had problems with zaptel compilation on suse(kernel-source-2.4.19.SuSE-342 // gcc 3.2.2 ) ... is shifting to red hat the only viable scenario...would be a pain cuz suse comes with sun java desktop system( just bought it !! ) ... any fixes would be a

Hi List, I am having some trouble with installing the latest version of ztdummy on a CentOS Kernel 2.6 system. I have installed a few Asterisk systems on Slackware Kernel 2.4.x without any issues, unfortunately there is no choice about this distro, or kernel as it has been preinstalled by someone else. And so I am in the dark with an unfamiliar distro and kernel. I am fairly sure the

Ok so I read the Linux 2.6 related README and finally compiled propperly, I thought but at the end I notice that lscpi does report the cards, but I cant modprobe wcfxo nor zaptel and I do have wcfxo.ko in the /lib/modules/2.6.8/extra/ directory, so what gives? This is a Debian Sarge, thanks! # # make clean starts here # make[1]: Entering directory `/usr/src/zaptel-1.4.0/menuselect' rm

It's nice to be able to define the list of asterisk modules we want to load from the /etc/sysconfig/zaptel file rather than directly in /etc/init.d/zaptel. I'm using nufone and don't require anything but the ztdummy (is the rtc-based module better, anyone?), so that's what I've put here. These are based on zaptel-1.0-RC1. John --- zaptel-1.0/zaptel.init.ole

Here's a call coming in over PSTN to dahdi/4, connected to a local extension dahdi/1: -- Executing [s at incoming-pstn-line:1] Answer("DAHDI/4-1", "") in new stack .......... -- Executing [s at incoming-pstn-line:6] Dial("DAHDI/4-1", "DAHDI/g0,36") in new stack -- Called g0 -- DAHDI/1-1 is ringing -- DAHDI/1-1 is ringing

Hi, I need to run ztdummy for Paging, but now that this is all become dahdi I don`t really know where to start. I did build dahdi before building asterisk, but that`s it. I find it hard to find any documentation referring to dadhi instead of zaptel. I have no Digium hardware, but I still need the ztdummy timer (or whatever it`s called now). How do I get myself going? Regards,

I've seen this consistently on three systems, with three different cards, and multiple versions of DAHDI. At first I thought the issue only occurred on newer, Nehalem-based, systems, but I reproduced it on a Core 2 Duo box as well. I've tested with dahdi-linux 2.2.0.2, dadhi- linux-complete 2.0.0+2.0.0, 2.1.0.2+2.1.0.2, and 2.2.0.2+2.2.0. The card is a Digium TE220B which uses the

I go to my Zaptel 1.4.0 folder and run ./configure; make linux26; make install and I don't see any errors. This is out of my modprobe.conf: install tor2 /sbin/modprobe --ignore-install tor2 && /sbin/ztcfg install torisa /sbin/modprobe --ignore-install torisa && /sbin/ztcfg install wcusb /sbin/modprobe --ignore-install wcusb && /sbin/ztcfg install wcfxo