man, 25.06.2007 kl. 15.47 +0200, skrev Dietmar Minniberger: > Hello! > > > > I’m testing and using Callweaver > > I’m using the latest spandsp and latest svn from Saturday or the > version from today rc4 > > > > The configuration is as follows: > > I’m using a Patton with SIP-Trunk for the E1-Gateway! > > A SIP-Trunk is to a Asterisk 1.4.5 for the calling! > > > > Now every incoming call went through Patton -> Callweaver-> Asterisk > > Just a Fax is directly connected to the Callweaver with T38 > > Incoming Fax are stored with RXFax and sent with TXFax > > Outgoing Fax are send directly. > > > > Normally it works fine, but about 2 to 5 times a day the callweaver is > hanging. > > In the log File the last message is always: > > > > Jun 25 09:00:39 WARNING[3053075376] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:01:01 NOTICE[3053341616] pbx_spool.c: Call completed to > LOCAL/[EMAIL PROTECTED] > > Jun 25 09:01:13 WARNING[3053341616] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:02:09 NOTICE[3054406576] pbx_spool.c: Call completed to > LOCAL/[EMAIL PROTECTED] > > Jun 25 09:05:44 WARNING[3053874096] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:11:54 WARNING[3052542896] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:17:54 WARNING[3053075376] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:18:35 WARNING[3053075376] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:18:58 WARNING[3053075376] pbx.c: Timeout, but no rule 't' in > context 'ankommend_etel' > > Jun 25 09:20:54 NOTICE[3060050864] sched.c: Attempted to delete > nonexistent schedule entry 2623! > > > > In this case sometimes it works with restart, sometimes I’ve the kill > process and restart callweaver. > Add a exten => t,1,Hangup in the ankommend_etel context. This will at least get rid of the warnings you are getting. Not sure why CallWeaver would hang, but it could be that lots of channels are hanging since they weren't hung up. The t exten could fix that. Give it a try. Please also show us your dialplan.
> > > Just one more information: > > Every time when I start callweaver there is following message in the > log file: > > Jun 25 09:25:01 WARNING[3060485040] timer.c: Requested a timer with > 1000000 nanosecond interval, but system timer reports a resolution of > 4000250 nanosec. Timing may be unreliable! > > > > Since rc4 there are 2 lines: > > Jun 25 09:24:02 WARNING[3055463344] timer.c: Requested a timer with > 3000000 nanosecond interval, but system timer reports a resolution of > 4000250 nanosec. Timing may be unreliable! > > Jun 25 09:25:01 WARNING[3060485040] timer.c: Requested a timer with > 1000000 nanosecond interval, but system timer reports a resolution of > 4000250 nanosec. Timing may be unreliable! > You need to recompile your kernel with a lower timer frequency. Good luck! > > > I’m using debian etch 4.01, > > > > I tried several configuration options: > > ./configure --enable-mysql=yes --with-cdr_mysql=yes > --with-chan_iax2=no --with-chan_woomera=no --with-chan_sccp=no > --with-app_sql_postgres=no > > > > If callweaver would work fine, I want the switch from Asterisk to > callweaver!!! > > > > Regards from Austria, > > Minniberger Dietmar > > e-mail: [EMAIL PROTECTED] > > Tel: +43 (7683) 5009 > > Fax: +43 (7683) 5009 4 > > > > > > > _______________________________________________ > Callweaver-dev mailing list > [email protected] > http://lists.callweaver.org/mailman/listinfo/callweaver-dev _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
