Status of misdn support

[Simon Richter]

Hello,

Tzafrir Cohen wrote:

>> The kernel patch is largely unneeded ATM because the initialisation in
>> the code is broken and depends on the correct init order, which can only
>> be done by loading the modules in the right order, so monolithic builds
>> are disabled by upstream anyway.

> Are those userspace 

? Is there a bit missing here?

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

>> Yes, but I'd prefer not to use that and build it out-of-tree. mISDN is
>> on its own schedule, chan_misdn is on its own schedule, and tying
>> asterisk releases to either of them is going to be painful.

> Not exactly. Digium have their own ISDN/BRI card and use misdn as the driver
> for it. Thus the ISDN channel is now safely in the tree and getting
> attention.

Well, you still need to use Zaptel (or ztdummy, which expects PC
hardware and is generally too intrusive for me to put onto a production
box where I need sub-millisecond accuracy for the RTC) if you want a
timing source, so zaphfc is at a certain advantage here.

> It was actually even rushed into 1.2.11 , even before 1.4 (in earlier
> 1.2.x versions there was an obsolete version that didn't work well and
> wa disabled by default).

According to the file list on p.d.o, it's not built yet; we only have a
file conflict on the conffile.

> So would you recommend to disable the build of chan_misdn in Asterisk?

If it is well-supported upstream then enabling it might work; however
this loses the possibility of forcing an isolated rebuild when ABI
breaks, so I'm ambivalent.

   Simon