Previously, if CDR filters were used so that
not all CDR records used all sections defined
in cdr_adaptive_odbc.conf, then warnings will
always be emitted (if each CDR record is unique
to a particular section, n-1 warnings to be
specific).
This turns the offending warning log into
a verbose message like the other one, since
this behavior is intentional and not
indicative of anything wrong.
ASTERISK-29494
Change-Id: Ifd314fa9298722bc99494d5ca2658a5caa94a5f8
} else if (entry->filtervalue
&& ((!entry->negatefiltervalue && entry->filtervalue[0] != '\0')
|| (entry->negatefiltervalue && entry->filtervalue[0] == '\0'))) {
- ast_log(AST_LOG_WARNING, "CDR column '%s' was not set and does not match filter of"
+ ast_verb(4, "CDR column '%s' was not set and does not match filter of"
" %s'%s'. Cancelling this CDR.\n",
entry->cdrname, entry->negatefiltervalue ? "!" : "",
entry->filtervalue);