On Tue, 3 Apr 2007, Peer Oliver Schmidt wrote: > Good Morning Armin, > > >> tried the patch, but it did not work. It waits quite a long time > >> before the chan-capi error message comes up, according to the time > >> stamp it is about 12 seconds. It is kind of strange, that the whole > >> startup process for asterisk usually takes only about 4-5 seconds. > > > That's too long, normaly the confirmation message arrives within a few > > msecs. So it seems that the driver isn't responding. > > > >> Do you need additional information? > > > > Which card/driver do you use? > > [EMAIL PROTECTED]:~# lspci -s 0:0e -v > 00:0e.0 Network controller: AVM Audiovisuelles MKTG & Computer System > GmbH A1 ISDN [Fritz] (rev 02) > Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH > FRITZ!Card ISDN Controller > Flags: medium devsel, IRQ 10 > Memory at ff001400 (32-bit, non-prefetchable) [size=32] > I/O ports at dcc0 [size=32] > > [EMAIL PROTECTED]:~# capiinit status > 1 fcpci running fcpci-dcc0-10 A1 3.11-07 0xdcc0 10 > > Driver from ubuntu edgy
I cannot tell anything about the AVM drivers. > > A debug log (capi trace) from the driver or kernelcapi helps to see > > what messages are wrong/missing. > > What is the best way to produce this? If the AVM driver can do that, I don't know. But on load of the module 'kernelcapi', you can specify the module parameter showcapimsgs=X where X is the verbose level. By default it is 0, which means no messges. You should set it to 3 to get the CAPI control messages on the kernel-console (logfile). Or even to 7 to have all CAPI messages (including data messages) which might be too much. Armin _______________________________________________ --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