[Asterisk-Users] Re: chan_capi-cm-0.6.4

[Armin Schindler]

On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
> On Tue, Feb 28, 2006 at 02:32:27PM +0100, Armin Schindler wrote:
> > On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
> > > On Tue, Feb 28, 2006 at 10:46:40AM +0100, Armin Schindler wrote:
> > > > Anyway, your config is set to DID mode. So chan_capi will wait for more 
> > > > digits (an INFO_IND with called-party-number) and if the already given 
> > > > destination number does not match the extensions.conf yet.
> > > Maybe that is the problem. The full DID information already is contained
> > > in the connect_ind according to the log I sent in the last Mail:
> > >   CalledPartyNumber               = <81>11
> > > [...]
> > >     -- CONNECT_IND (PLCI=0x101,DID=11,CID=650621xxxx,CIP=0x10,CONTROLLER=0x1)
> > >        > ISDN1: msn='*' DNID='11' DID
> > > 
> > > In Austria the PTP will send only the DID information, not the whole
> > > number, so "11" is all that is sent for DID.
> > 
> > That is okay, the dialplan just need to have a match.
> > 
> > > And according to my
> > > dialplan "11" should call one of my ZAP channels.
> > 
> > Okay, but in DID mode chan_capi waits for additional INFO_INDs until
> > a) a dialplan match is found or
> That condition should be fulfilled, I have
> [...]
> exten => 11,1,Noop()
> exten => 11,2,Noop(11)
> exten => 11,3,Dial(${UNTEN})
> exten => 11,4,Busy()
> exten => 11,104,Busy()
> 
> in my dialplan. But the call isn't seen by my dialplan.

That is correct so far.
 
> > > Maybe chan_capi should have a timeout waiting for more info_ind and if
> > > the timeout is reached pass the call to asterisk anyway?
> > 
> > What for? The dialplan rules should give you enough to make this possible.
> See above: Seems the dialplan match isn't detected??

It will be detected when chan_capi gets the signal to check it
(SENDING-COMPLETE/SETUP INFO_IND, or normal CONNECT_IND in MSN mode with 
immediate=yes).
 
Armin