Bug#389238: asterisk-chan-capi: Cannot reproduce #389238 with asterisk-classic

[Lionel Elie Mamane]

On Thu, Sep 28, 2006 at 11:24:37AM +0300, Tzafrir Cohen wrote:
> On Thu, Sep 28, 2006 at 09:59:01AM +0200, Lionel Elie Mamane wrote:

>> I cannot reproduce this with asterisk-classic, wether the global
>> section of modules.conf contains chan_capi.so=yes or not.

> Clarification: the asterisk-bristuff package currently contains
> Junghanns' version of chan_capi (from bristuff).

Yes, but Christoph Kling, in
<0BC14E02EE4AA348BFA09E42718EEBEF02945F at beta.familiekling.de>
archived at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389238;msg=15
says he had the same symptoms with asterisk-classic, thus hinting at
another cause than what you had diagnosed.

> What do you think: should we keep that chan_capi as part of bristuff
> and make the cha_capi package require asterisk-classic? Dump it and
> tell all chan_capi users to install chan_capi ?

Is there any advantage to the bristuff chan_capi (additional feature,
specific bug corrected)? I don't know of any. As such, I'd say dump
the bristuff chan_capi. But it won't solve Christoph Kling's
problem. And this relies on the "no advantage to the bristuff
chan_capi" I'm not sure of. If the bristuff chan_capi really has
advantages, the ideal situation would be that people can choose,
including using asterisk-chan-capi _and_ bristuff (for the popular
multi-BRI cards). For example that the bristuff chan_capi is separated
in its own package, or that asterisk-chan-capi disables it on install,
or something like that.

-- 
Lionel