In most cases, flushing an audiohook is not a bad thing, nor is it something to be worried about. That's why it's a debug message. If you want it in your logs, then set the core debug level to 1 so it shows up. You will get more messages than you are used to seeing, but by only setting the core debug level to 1, you will not get as badly flooded as you might if you were to set the level higher.
On Fri, Jan 29, 2016 at 4:15 AM, Tomec Martin <to...@ipex.cz> wrote: > Hi all, > > > > we are solving issue with mixmonitor – in production asterisk, there are > sometimes gaps in recordings (missing syllables), but we cannot reproduce > it in test enviroment. > > I suppose it is caused by frames flushing in audiohook.c: > > > > *if* (*ast_test_flag(audiohook, **AST_AUDIOHOOK_TRIGGER_SYNC**)* > && other_factory_samples && (our_factory_ms - other_factory_ms > > AST_AUDIOHOOK_SYNC_TOLERANCE)) { > > *ast_debug(1, **"Flushing audiohook %p so it remains in > sync\n"**, audiohook)*; > > ast_slinfactory_flush(factory); > > ast_slinfactory_flush(other_factory); > > } > > > > My question is, why it is not logged as a warning. I think that warning > could help to diagnose the problem in production enviroment. Am I missing > some „rules“ for log levels, or am I right? > > > > Thanks for any hint > > Martin Tomec > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev