Bug 1033847 - asterisk-misdn is outdated
Summary: asterisk-misdn is outdated
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: asterisk
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-23 18:42 UTC by Thomas Sailer
Modified: 2014-06-19 16:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-19 16:48:12 UTC
Type: Bug


Attachments (Terms of Use)

Description Thomas Sailer 2013-11-23 18:42:17 UTC
Description of problem:
The misdn channel driver development has stopped long ago. It only works with mISDN, which itself only works with the mISDN v1 kernel API, which has been replaced incompatibly circa 2.6.30.

This channel driver should be removed and replaced with chan_capi.

Version-Release number of selected component (if applicable):
asterisk-misdn-11.5.1-2.fc19

How reproducible:
always

An initial chan_capi asterisk package can be found here:
http://sailer.fedorapeople.org/asterisk-capi-1.1.6-1.fc19.src.rpm

Comment 1 Jeffrey C. Ollie 2013-12-29 22:47:36 UTC
Is chan_capi going to be included in Asterisk proper?  I have no way to test mISDN/capi so I'm not going to add patches to the Asterisk package or take on a new package.

Comment 2 Thomas Sailer 2013-12-29 23:15:40 UTC
Unlikely.

I'd be willing to submit the capi channel driver package for review and maintain it, if I get the possibility to update the required components (mISDNuser update).

Comment 3 Jeffrey C. Ollie 2013-12-29 23:28:50 UTC
I don't think that it'd be too hard to become a maintainer for the mISDN package:

https://admin.fedoraproject.org/pkgdb/acls/name/mISDN

chan_misdn isn't building in rawhide anyway at the moment so now would be a good time to get chan_capi packaged.

Comment 4 Jeffrey C. Ollie 2014-06-19 16:48:12 UTC
I'm going to close this out as there's nothing to be done from an Asterisk packaging point of view.


Note You need to log in before you can comment on or make changes to this bug.