[Asterisk-Users] CAPI unable to handle busy()
Armin Schindler
armin at melware.de
Mon Jan 2 07:28:59 MST 2006
On Mon, 2 Jan 2006, Karsten Wemheuer wrote:
> Hello Armin,
>
> On Mo, 02.01.2006 Armin Schindler wrote:
> > On Mon, 2 Jan 2006, Karsten Wemheuer wrote:
> > > Hello,
> > >
> > > first of all, I say "Happy New Year" to this list!
> > >
> > > While using asterisk 1.2.1 with bristuff-0.3.0-PRE-1d (which includes
> > > chan_capi 0.4.0-PRE1), I ran into the following problem.
> > >
> > > I want to signal "busy" to an incoming call, but that doesn't work.
> > >
> > > The dialplan looks like this:
> > > exten => 22715292,1,Busy
> > > (The extension is ok and works fine, if I use other applications like
> > > Dial)
> >
> > chan_capi from junghanns/bristuff does not support that.
> > I suggest using the new chan_capi-cm-0.6.2
> >
>
> thanks for the quick response. How can I implement bristuff-patch and
> Your new chan_capi? I need a version with both, ZAP-HFC and CAPI. So the
> question is, how can I exclude chan_capi from the bristuff-patches?
I don't think it is necessary to exclude it. Just build chan_capi-cm and
overwrite chan_capi.so as well as remove the app_capi* modules from your
installation.
Armin
More information about the asterisk-users
mailing list