It really depends on the application. app_conference does wonderfully for long conferences without a lot of entry/exit and no playing of audio files.
The issues with the double-free crashes that we've had all seem to be caused by playing of audio files(like the entry/exit sounds or the DTMF broadcast). But these functions use the app_conference code that was already existing to play audio files from manager API commands so the issue was there it just wasn't as tested because not many people use the manager command a lot to play audio in conferences. The other issue we had with app_conference was using it in high-volume VICIDIAL outbound production(thousands of entry/exit actions per hour) where it would always fail after 1-8 hours. In this case there wasn't a crash, but strangely app_conference just seemed to stop working like the engine died. Everything else in Asterisk kept working but you couldn't do anything in app_conference without stopping and starting Asterisk again. MATT--- On 7/12/06, jeff oconnell <[EMAIL PROTECTED]> wrote:
On 7/12/06, Henry J. Cobb <[EMAIL PROTECTED]> wrote: > When I've tried it, app_conference always crashed within the hour. that's strange. we've use app_conference for months and months on end without incident. are you building app_conference from the main svn trunk? or are you using matt's VD_app_conference that he mentioned a couple posts ago? j- _______________________________________________ --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
_______________________________________________ --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
