>> >> The error is only visible however if I run * with -vvvvv
>> (but I guess I shouldnt see these messages nonetheless)?
>
> No, I still have these messages, and was hoping RC5 would fix them. Nice to > know that upgrading wont help :-(
Are you running asterisk with -vvvvvv too? If I run it without verbose mode on I do not get these messages. Klaus-Peter Junghanns just replied to the message to and confirmed that this message is normal expected behaviour
> Do you get calls which stop in the middle of the conversation as well?
No but it is a completely new setup and line and I havent used it much.
You may try putting busydetect=no in /etc/asterisk/zapata.conf, I have seen several messages on the list about calls getting cut off and this being the solution.
The busydetect=no did the trick here.
Remco, are you running * on a SMP system ? I cant get the bristuffed thing stable on my P4 HT. I am now running it with i4l and HT disabled, but since it also hosts our internal communication application coded in php with postgres as backend it would be nice to be able to run a second thread when the database is busy.
Cheers! Remco
Michiel.
_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
