On Wed, 14 Dec 2005, stéphane plichon wrote:
> Armin Schindler wrote:
> > On Wed, 14 Dec 2005, stéphane plichon wrote:
> >
> context=capi-in
> devices=2
> >>>
> >>>
> >>>This is just one section which two sets of options. You need to define two
> >>>sections with [...]. See README.
> >>>
Armin Schindler wrote:
> On Wed, 14 Dec 2005, stéphane plichon wrote:
>
context=capi-in
devices=2
>>>
>>>
>>>This is just one section which two sets of options. You need to define two
>>>sections with [...]. See README.
>>>
>>>Armin
>>>
>>>
>>
>>no in or out call if i do that (with or wit
On Wed, 14 Dec 2005, stéphane plichon wrote:
> >>context=capi-in
> >>devices=2
> >
> >
> > This is just one section which two sets of options. You need to define two
> > sections with [...]. See README.
> >
> > Armin
> >
> >
>
> no in or out call if i do that (with or without [interfaces]):
>>context=capi-in
>>devices=2
>
>
> This is just one section which two sets of options. You need to define two
> sections with [...]. See README.
>
> Armin
>
>
no in or out call if i do that (with or without [interfaces]):
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain
On Wed, 14 Dec 2005, stéphane plichon wrote:
> stéphane plichon wrote:
> > stéphane plichon wrote:
> >
> >>Hi all,
> >>
> >>currently i running * 1.0.9 with chan_capi 0.3.5
> >>
> >>my first problem is:
> >>
> >>in incoming call, when BCHAN is full in contr1 incoming call on contr2
> >>are not ans
stéphane plichon wrote:
> stéphane plichon wrote:
>
>>Hi all,
>>
>>currently i running * 1.0.9 with chan_capi 0.3.5
>>
>>my first problem is:
>>
>>in incoming call, when BCHAN is full in contr1 incoming call on contr2
>>are not answered with error :
>>
>>chan_capi.c:1953 in capi_handle_msg: receiv
rs Mailing List - Non-Commercial Discussion"
Sent: Tuesday, December 13, 2005 5:09 PM
Subject: Re: [Asterisk-Users] chan_capi AVM C2
stéphane plichon wrote:
Hi all,
currently i running * 1.0.9 with chan_capi 0.3.5
my first problem is:
in incoming call, when BCHAN is full in contr1 incom
On Tue, 13 Dec 2005, stéphane plichon wrote:
> stéphane plichon wrote:
> > Hi all,
> >
> > currently i running * 1.0.9 with chan_capi 0.3.5
> >
> > my first problem is:
> >
> > in incoming call, when BCHAN is full in contr1 incoming call on contr2
> > are not answered with error :
> >
> > chan_
stéphane plichon wrote:
> Hi all,
>
> currently i running * 1.0.9 with chan_capi 0.3.5
>
> my first problem is:
>
> in incoming call, when BCHAN is full in contr1 incoming call on contr2
> are not answered with error :
>
> chan_capi.c:1953 in capi_handle_msg: received a call waiting CONNECT_IN
Philipp von Klitzing wrote:
> Hi!
>
>
>>currently i running * 1.0.9 with chan_capi 0.3.5
>
>
> Try chan_capi-cm instead and see if it helps.
>
> Cheers, Philipp
>
>
>
compiling 0.5.4 when there was more than 2 call i got :
ERROR[6060]: chan_capi.c:2324 capi_handle_connect_indication: recei
Hi!
> currently i running * 1.0.9 with chan_capi 0.3.5
Try chan_capi-cm instead and see if it helps.
Cheers, Philipp
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
currently i running * 1.0.9 with chan_capi 0.3.5
my first problem is:
in incoming call, when BCHAN is full in contr1 incoming call on contr2
are not answered with error :
chan_capi.c:1953 in capi_handle_msg: received a call waiting CONNECT_
12 matches
Mail list logo