On Tue, Sep 8, 2009 at 5:08 AM, Erik de Wild<[email protected]> wrote: > using mixmonitor might not be such a good idea. afaik the mixing of > the recordings of the two channels starts after ending the call > causing a high cpu load.
Incorrect. The 'mix' in Mixmonitor() is that two legs of a call are mixed together as the recording happens. It is Monitor() that works in the way you describe, although 'high cpu load' is dependent on how you mix. It would be 'bursty' cpu load if you choose to mix as soon as a recording completes. Since Mixmonitor() is mixing as the recording happens, there is instantly a retrievable recording when the recording completes. _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
