On Fri, Feb 24, 2006 at 10:43:31AM +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? Quite current. Checkout of mqueue branch from three days ago. Well I'll report a bug.
> > > If you use mISDN, why don't you use chan_misdn? > > How reliable is that? Any experience? > > I don't have any experience with mISDN. I just noticed the big work going on > with mISDN and I assume that the support is good. I'll try this as a second route. I'd prefer chan_capi though, because I have used it for quite some time ... Thanks a lot for your help. Ralf -- Ralf Schlatterbeck email: [EMAIL PROTECTED] FAX: +43/2243/26465/23 _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
