Status of misdn support

[Tzafrir Cohen]

On Tue, Aug 29, 2006 at 11:33:37PM +0200, Simon Richter wrote:
> Hello,
> 
> Alessandro Polverini wrote:
> 
> > I tried to send Simon Richter a couple of mails on the subject but I had
> > no response.
> 
> Yes, I'm busy. Your mail is still flagged "to do". :-/
> 
> No, it should not be released with etch. There are lots of issues in the
> code that need to be worked out before. The fact that it is in use in
> production systems means that these systems are not doing anything else,
> never reconfigure their ports or start/stop asterisk. Fixing that will
> require changing the API, the ABI and a zillion places in the kernel.

Let's look at the scope of the package.

We have the basic package, providing kernel support and basic userspace
tools. What is its status?

The kernel support package seem overly complex to me. It aims at
generating not only a modules sources list but also a kernel patch. Its
build is very complex and requires quite a few kernel source trees.

I've tried a while ago to simplify it into a zaptel-like modules-only
package. It seemed to work. But I gave it up as I had no hardware and no
Asterisk support to go with.

I can try to reproduce that package. The infrastructure for building
modules has only since improved.


Then there is the asterisk-misdn package. That one is not necessary
anymore, as it is part of the official Asterisk (source) package.


Note that misdn is a rather low priority for me at the moment.

-- 
Tzafrir Cohen         sip:tzafrir at local.xorcom.com
icq#16849755          iax:tzafrir at local.xorcom.com
+972-50-7952406          jabber:tzafrir at jabber.org
tzafrir.cohen at xorcom.com     http://www.xorcom.com