status of misdn again

[Tzafrir Cohen]

On Tue, Jan 09, 2007 at 04:08:04AM +0100, Simon Richter wrote:
> Hi,
> 
> Tzafrir Cohen wrote:

> >Making chan_misdn in Asterisk work, mainly. There is now (recent 1.2 and
> >1.4) chan_misdn in Asterisk. I'm not sure how good it is, but people are
> >reported to have used it and survived the exeprince.
> 
> Indeed, however kernel ABI changed again just a week ago, so compiling 
> it as an external module is giving us the advantage of not having to 
> synchronise asterisk uploads with mISDN.
> 
> chan_misdn as an external package is currently uninstallable as the 
> asterisk config package brings a misdn.conf file.

But chan_misdn is a separate package. It sits on top of the
userspace misdn library. So getting it to work is a different issue.
Right?

Is there actually any point in using an external chan_misdn package now
that it has been merged into Asterisk?

> 
> >I packaged a new package mainly as a proof of concept that a simple
> >external module package can work. That is not a usable package, indeed.
> >It does not even have misdn-init or any alternative properly packaged.
> 
> Neither has mine, basically because all of these approaches are wrong.
> 
> The right thing to do would be hotplug integration coupled with the 
> kernel enforcing sanity.

Hotplug? You probably mean udev. Don't those modules load automatically
by PCI IDs? What needs to be hotplugged?

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