Bug 783890

Summary: RFE: Please update to 2.6.0
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: dahdi-toolsAssignee: Jeffrey C. Ollie <jeff>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: amessina, bruno, itamar, jeff
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-17 18:29:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Bruno Wolff III 2012-01-23 06:12:02 UTC
Description of problem:
dahdi-tools and dahdi-linux 2.6.0 are now available. Currently rawhide has 2.4.1.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Anthony Messina 2012-04-25 14:19:10 UTC
dahdi 2.6.1 is now available.

Comment 2 Bruno Wolff III 2012-04-25 14:32:08 UTC
Is there a technical issue blocking upgrades for dahdi-tools or time? I use dahdi in rawhide and I should be able to find time to keep rawhide up to date if you want another co-maintainer?

Comment 3 Anthony Messina 2012-04-28 17:09:52 UTC
Gentlemen, in looking at this, I found that 2.6.1 needs a few tweaks to allow Asterisk 10.3.1 to build with proper DAHDI support, namely the addition of dahdi_config.h to the devel package.  My changes are here (all based on Fedora's upstream work mostly by Jeff):

http://messinet.com/rpms/changeset/17519ad/dahdi-tools

I still have not been able to address the systemd issue--I'll likely need help on that.

Comment 4 Bruno Wolff III 2013-08-17 17:30:22 UTC
2.7.0 has been built for rawhide.
I haven't applied Anthony's change yet, but have verified that tools 2.7 doesn't include that header, so it will need to be done.
Also I noticed he removed --disable-static which was generating a warning from configure. So I'll remove that as well.

Comment 5 Bruno Wolff III 2013-08-17 17:40:33 UTC
Does user.h really need to be included as both user.h and dahdi_config.h?

I have done that for now in my latest build. After it finishes I'm going to close this bug. If there still is an issue with user.h / dahdi_config.h that should probably be opened as a separate bug, since the subject of this one would be misleading.

Comment 6 Bruno Wolff III 2013-08-17 18:29:01 UTC
I am seeing an issue on reboot, but it might be my latest dahdi-linux rebuild. If it is dahdi-tools, I'll file a new bug if I can't fix it right away.

Comment 7 Anthony Messina 2013-09-02 16:57:15 UTC
(In reply to Bruno Wolff III from comment #4)
> 2.7.0 has been built for rawhide.
> I haven't applied Anthony's change yet, but have verified that tools 2.7
> doesn't include that header, so it will need to be done.
> Also I noticed he removed --disable-static which was generating a warning
> from configure. So I'll remove that as well.

Thanks, Bruno.  I've made some other changes [1] as well.  Basically, with Tzafrir's changes in dahdi-tools-2.7 including "--enable-pinned", it appears as though the initscript may eventually be phased out in favor of running dahdi_config via udev rules.  I have no confirmation from upstream on this, but I *can* confirm that since June, I have the dahdi service disabled and after setting the DAHDICONFDIR to /etc/dahdi, (done in my spec file):

sed -ri 's:(\s)?#(export DAHDICONFDIR=")/tmp/xortel/dahdi("):\1\2/etc/dahdi\3:' handle_device

udev properly initializes my card (which is not a Xorcom card).  I also needed to remove wctdm24xxp from the dahdi.blacklist.conf file.



# All via udev... No dahdi service
[    6.726323] wctdm24xxp 0000:02:08.0: setting latency timer to 64
[    8.319107] wctdm24xxp 0000:02:08.0: vpmoct: Detected firmware v1.12 Serial: 5VPMOCT032LF-B    DM99140010129 
[    9.895492] wctdm24xxp 0000:02:08.0: Port 1: Installed -- AUTO FXO (FCC mode)
[    9.895503] wctdm24xxp 0000:02:08.0: Port 2: Installed -- AUTO FXO (FCC mode)
[    9.895505] wctdm24xxp 0000:02:08.0: Port 3: Installed -- AUTO FXS/DPO
[    9.895507] wctdm24xxp 0000:02:08.0: Port 4: Installed -- AUTO FXS/DPO
[    9.896062] wctdm24xxp 0000:02:08.0: Found a Wildcard TDM: Wildcard AEX410 (0 BRI spans, 4 analog channels)



1. https://messinet.com/rpms/browser/dahdi-tools/dahdi-tools.spec?rev=05ad8d3da097e0b01cc36c4fbe961a13816a3eb8