| Summary: | ASTERISK-22272: [patch] Unexepected behaviour with adaptive odbc filter | ||
| Reporter: | Jordi Llull ChavarrÃa (jllull) | Labels: | |
| Date Opened: | 2013-08-09 03:33:38 | Date Closed: | 2013-10-23 11:42:03 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | CDR/cdr_adaptive_odbc |
| Versions: | 11.4.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) cdr_adaptive_odbc.diff | |
| Description: | I was playing with our CDR configuration and I found an annoying behaviour when trying to replace the src column in some cases. My {{cdr_adaptive_odbc.conf}} contains something like this:
[replace-src] connection=asterisk table=cdr alias source => src filter source != [dont-replace-src] connection=asterisk table=cdr filter source => So if you set CDR(source) in the dialplan it works great. However if you don't set it it'll insert two rows in the CDR. That's because it won't check filters if the value is not set! The attached patch solves the problem by avoiding inserting the CDR if the column is not set and there's a non-blank filter for it. | ||
| Comments: | |||