similar to: New Versions of Asterisk, Asterisk-addons, Zaptel, and DAHDI

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 the first offical release of the Digium Asterisk Hardware Device Interface (DAHDI). The list of packages released today includes: dahdi-linux 2.0.0 dahdi-tools 2.0.0 dahdi-linux-complete 2.0.0+2.0.0 Both dahdi-linux and dahdi-tools are required to enable DAHDI support in your system. You will need to install dahdi-linux first, then

Hi All, I have recently installed a TC400B card into a system and am trying to get it to work. As far as I ca tell from the docco on Digiums website, there is no config as such unless you want to enable / disable only 1 codec, otherwise by default it runs as 92 channels of either. I have tried asterisk 1.4.9, 1.4.10 and 1.4.10.1 along with zaptel 1.4.4 and addons 1.4.2. The zaptel modules

Hello all, I have a TC400B Digium card in order to deal with transcoding and I have some trouble using it, I have a timer synchronisation problem! I would be very grateful if you have any idea to help me? It seems that the card is not correctly synchronised to the system because when I speak to one side, the sound takes 5 seconds to go to the other side, and increasing, after 30 seconds of call,

The Asterisk.org development team is pleased to announced the release of Asterisk release candidates 1.6.0.7-rc2, 1.6.1.0-rc3, and beta release 1.6.2.0-beta1. Additionally, new release candidates of Asterisk-Addons 1.6.0.2-rc1 and 1.6.1.0-rc3 have been created. Note that the 1.6.1 series of Asterisk-Addons is compatible with both Asterisk 1.6.1 and 1.6.2 branches. These releases are available for

The Asterisk.org development team has released Asterisk versions 1.4.22-rc5 and 1.6.0-rc6, as well as Zaptel version 1.4.12.1. These releases are available for immediate download from http://downloads.digium.com/. This update for Zaptel includes a fix for an issue that would cause the build to fail if no firmware was selected to be installed. For a full list of changes, see the ChangeLog:

The Asterisk.org development team has released Asterisk versions 1.4.22-rc5 and 1.6.0-rc6, as well as Zaptel version 1.4.12.1. These releases are available for immediate download from http://downloads.digium.com/. This update for Zaptel includes a fix for an issue that would cause the build to fail if no firmware was selected to be installed. For a full list of changes, see the ChangeLog:

hello, I tried to compil asterisk-addons-1.6.2.0-rc1, and I have that error: [CC] res_config_mysql.c -> res_config_mysql.o res_config_mysql.c:1367: error: unknown field ?update2_func? specified in initializer res_config_mysql.c: In function ?parse_config?: res_config_mysql.c:1432: error: ?CONFIG_STATUS_FILEMISSING? undeclared (first use in this function) res_config_mysql.c:1432: error:

Yesterday, a low-duty production server that I maintain core-dumped. At the time there were only around 2 calls going through it. The strace on the screen made it look like it was caused by Dahdi. The machine is running asterisk-1.6.0.3 dahdi-linux-2.1.0.3 dahdi-tools-2.1.0.2 asterisk-addons-1.6.0 Kernel version 2.6.28 There is a genuine TDM400P (populated witrh 2xFXO cards and 2xFXS cards.

The Asterisk.org development team is proud to announce the releases of Asterisk 1.4.22 and 1.6.0. ================================================================= === Asterisk 1.4.22 ============================================= ================================================================= Asterisk 1.4.22 includes a large number of bug fixes for the 1.4 release series of Asterisk. 1.4.22

The Asterisk.org development team is proud to announce the releases of Asterisk 1.4.22 and 1.6.0. ================================================================= === Asterisk 1.4.22 ============================================= ================================================================= Asterisk 1.4.22 includes a large number of bug fixes for the 1.4 release series of Asterisk. 1.4.22

Hi, It's not clear to me which asterisk version drops support for zaptel in favor of dahdi. Dahdi and zaptel can "coexist" in some 1.4 versions but it seems that from 1.4.22 onward, chan_zap.so is not built. Documentation within the 1.4.23.1 tarball indicates that one can keep using the zap*.conf files by switching an option in asterisk.conf. Is this true or should I forcefully

We recently updated our Asterisk (1.4.24) box from Zaptel (1.4.12.1) to Dahdi (2.1.0.4). Everything seemed to go smooth with the exception of meetme. Meetme seems to not be able to find a zap channel for conferencing. We use voice introductions in our conference bridge and it seems to break that feature. The error from the console is.... # app_meetme.c:2593 find_conf: No Zap channel available for

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

Tzafrir Cohen a ?crit : > On Tue, Mar 17, 2009 at 07:16:26PM +0100, Administrator TOOTAI wrote: > >> Hi, >> >> We installed the latest 1.4.24 on a test machine and can't get zaptel >> nor dahdi compile. It's a Linux Debian Etch. Errors we have: >> >> keewi:/usr/src/dahdi-linux-2.1.0.4# make >> make -C /lib/modules/2.6.18-custom.2/build

Last week some changes were made in the Zaptel source code repository referencing a new name (DAHDI) for that code. This has caused some discussion (and confusion) in the community, since it occurred before we had made a public announcement of the name change. However, that announcement is now official, and is located here:

The Asterisk development team is pleased to announce the release of Zaptel 1.2.13. This release contains a large number of bug fixes, an important performance improvement for most Digium cards, and support for new Digium hardware and some significant improvements in the XPP driver for Xorcom's Astribank hardware. In detail: * A modification was made to the drivers for all Digium PCI cards

The Asterisk development team is pleased to announce the release of Zaptel 1.2.13. This release contains a large number of bug fixes, an important performance improvement for most Digium cards, and support for new Digium hardware and some significant improvements in the XPP driver for Xorcom's Astribank hardware. In detail: * A modification was made to the drivers for all Digium PCI cards