On Tue, 3 Apr 2007, Peer Oliver Schmidt wrote: > Hello Armin, > > here are the results, after modprobe kernelcapi showcapimsgs=3 > > --------/var/log/kern.log ... > Apr 3 15:06:22 server42 kernel: [255120.102281] capi20: Rev 1.1.2.7: started > up with major 68 (middleware+capifs) > Apr 3 15:06:35 server42 kernel: [255133.725987] kcapi: appl 1 up > Apr 3 15:06:35 server42 kernel: [255133.727235] kcapi: put [0x1] id#1 > FACILITY_REQ len=18 > Apr 3 15:06:35 server42 kernel: [255133.727712] kcapi: got [0x1] id#1 > FACILITY_CONF len=26 > Apr 3 15:06:35 server42 kernel: [255133.729933] kcapi: appl 1 down > Apr 3 15:06:35 server42 kernel: [255133.730585] kcapi: appl 1 up > Apr 3 15:06:35 server42 kernel: [255133.731478] kcapi: put [0x1] id#1 > LISTEN_REQ len=26 > Apr 3 15:06:52 server42 kernel: [255150.690252] kcapi: appl 1 down > > ---------------- > > At 15:06:35 the loading stopped. > > Is this helpful, or do you need a higher verbosity?
Well, it confirmes what I have expected, but I cannot tell why it happens. The driver doesn't respond to the LISTEN_REQ command, that's why chan-capi shows an error. So with this info, the driver is the problem. Can you please do the same with 'showcapimsgs=2'? It may give more info on the commands itself, maybe some parameters are wrong here. 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