DAHDI-Linux And DAHDI-Tools Now Available

Home » Uncategorized » DAHDI-Linux And DAHDI-Tools Now Available
Uncategorized 4 Comments

The Asterisk Development Team has announced the releases of:

This release is available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete

*** THIS RELEASE FIXES CentOS 6.5 “PDE_DATA” build issue ***

dahdi-linux-complete tarballs now include all firmware necessary to build without an internet connection.

Issues closed in this release:

Shortlog of changes since v2.7.0.1:
Shaun Ruffell (2):
dahdi: CentOS 6.5 backported PDE_DATA definition.
dahdi: Fix previous CentOS 6.5 commit.

The diffstat from the v2.7.0.1 release:
include/dahdi/kernel.h | 12 ++++++++++++
1 file changed, 12 insertions(+)

For a full list of changes in these releases, please see the shortlog at:

4 thoughts on - DAHDI-Linux And DAHDI-Tools Now Available

  • Hello Asterisk,

    Tuesday, December 3, 2013, 11:28:31 AM, you wrote:

    I tried DAHDI-Linux-v2.8.0-rc5 and now this and I keep having to go back to DAHDI-Linux-v2.7.0.1 because my HPEC licenses won’t load under the new versions? Is there something I’m missing that I have to do diffeerent

    I always quit Asterisk and run “service dahdi stop” until it exits clean, usually it takes 2 tries, then run “service dahdi start” which always in the past has loaded the HPEC drivers and license and then DAHDI, but with the newest releases it fails loading the HPEC stuff.

    I’ll happily post a bug report, but I’d like to know if I’m just being stupid before I do that.

    — Ira

  • Hello Shaun,

    Tuesday, December 3, 2013, 7:20:34 PM, you wrote:

    Yes, it was me. I’ve had to copy the HPEC stuff from version to version so many time and it’s been hectic and I forgot all about it. Solved the problem in both the current and beta versions. Thanks so much for the help.

    — Ira

  • And thank you for trying out the release candidates and reporting issues. We really do appreciate it.

    Cheers, Shaun