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

[Armin Schindler]

On Tue, 28 Feb 2006, Ralf Schlatterbeck wrote:
> On Fri, Feb 24, 2006 at 10:43:31AM +0100, Armin Schindler wrote:
> > On Fri, 24 Feb 2006, Ralf Schlatterbeck wrote:
> > > On Thu, Feb 23, 2006 at 02:45:25PM +0100, Armin Schindler wrote:
> >  
> > > > > Interesting is, that I receive an INFO_IND *before* the CONNECT_IND.
> > > > > This looks like an interesting variation of Austrian ISDN to me.
> > > > 
> > > > Maybe it is a variation of the ISDN line, but the driver should fix that.
> > > > Sending INFO_IND with a call-reference (PLCI) which is assigned by 
> > > > CONNECT_IND later, is just an error of the isdn driver.
> > > You mean, the capi part of misdn? Should I report a bug against mISDN?
> > 
> > Yes. Maybe it is already fixed in mISDN and you have an older version?
> 
> OK, I've reported a bug to mISDN. With the patch from the Karsten Keil
> in the mantis tracker:
> issue: https://www.isdn4linux.de/mantis/view.php?id=40
> I'm now gettig connect_ind and info_ind in the correct order (asterisk
> capi debug + verbose 15 log attached). The call still does not proceed
> in asterisk (the disconnect comes whe I unplug the ISDN-Line after
> several minutes). I've also attached my capi.conf and relevant portions
> of the dialplan. The version of mISDN is mqueue from yesterday with the
> mantis-tracker patch applied.
> 
> Any ideas what I should try next?

Well, the error message from mISDN:
  > CAPI INFO 0x3301: Protocol error layer 1 (broken line or B-channel removed by signalling protocol)

seems to be very clear. The ISDN line is not working or the used protocol is 
wrong.

Armin