Hello Armin, >> [EMAIL PROTECTED]:~# grep capi /var/log/asterisk/messages >> >> [Mar 31 16:17:03] ERROR[3850] chan_capi.c: Unable to listen on contr1 >> (error=0x100f) >> >> Is this helpful, or do you need more information? > > Yes, at this state it might be possible that less CPU power causes > problems. The 'listen' command expects an answer and maybe it is coming too > late. Can you please try the patch below? > > Index: chan_capi.c > =================================================================== > --- chan_capi.c (revision 436) > +++ chan_capi.c (working copy) > @@ -631,7 +631,7 @@ > error = LISTEN_CONF_INFO(&CMSG); > break; > } > - usleep(20000); > + usleep(100000);
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. Do you need additional information? -- Best regards Peer Oliver Schmidt PGP Key ID: 0x83E1C2EA _______________________________________________ --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