I would suggest upgrading to at least 1.4.18. I was able to run it for about 2 weeks and almost one million calls before I could get it to crash, and the 1.4.19RC2 seems to fix even more of the locking issues as well. I know a lot of these problems still existed under 1.4.17.
MATT--- On 3/18/08, Patrick <[EMAIL PROTECTED]> wrote: > > On Tue, 2008-03-18 at 07:04 -0400, Al Baker wrote: > > Could you clarify what you mean by a "Dead Locked Channel" ? > > That is not a term I am familiar with used in context to "channels", > > databases yes, channels ??? > > > A channel got locked but never unlocked causing all sorts of funky > behavior. It's a bug. The developers have fixed a ton of these deadlocks > in 1.4 so it's usually a good plan to try the latest and greatest > version to see if the problem goes away. > > I'm not very familiar with queue setups but Doug Lytle's advice sounds > like a plan. And try 1.4.19-rc2 to see if the deadlock problem persists. > If it does then please file a bug so it can be looked at. > > Regards, > > Patrick > > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users