Remove inconsistency in CEL eventtype for user defined events.
The CEL eventtype field for ODBC and PGSQL backends should be USER_DEFINED instead of the user defined event name supplied by the CELGenUserEvent application. If the field is output as a number, the user defined name does not have a value and is always output as 21 for USER_DEFINED and the userdeftype field would be required to supply the user defined name. The following CEL backends (cel_odbc, cel_pgsql, cel_custom, cel_manager, and cel_sqlite3_custom) can be independently configured to remove this inconsistency. * Allows cel_manager, cel_custom, and cel_sqlite3_custom to behave the same way. (closes issue ASTERISK-17189) Reported by: Bryant Zimmerman Review: https://reviewboard.asterisk.org/r/1669/ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@353648 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Showing
- cel/cel_manager.c 31 additions, 3 deletionscel/cel_manager.c
- cel/cel_odbc.c 25 additions, 1 deletioncel/cel_odbc.c
- cel/cel_pgsql.c 25 additions, 8 deletionscel/cel_pgsql.c
- cel/cel_tds.c 7 additions, 5 deletionscel/cel_tds.c
- configs/cel.conf.sample 7 additions, 0 deletionsconfigs/cel.conf.sample
- configs/cel_custom.conf.sample 1 addition, 0 deletionsconfigs/cel_custom.conf.sample
- configs/cel_odbc.conf.sample 8 additions, 1 deletionconfigs/cel_odbc.conf.sample
- configs/cel_pgsql.conf.sample 5 additions, 0 deletionsconfigs/cel_pgsql.conf.sample
- configs/cel_sqlite3_custom.conf.sample 1 addition, 0 deletionsconfigs/cel_sqlite3_custom.conf.sample
- main/cel.c 9 additions, 5 deletionsmain/cel.c
Loading
Please register or sign in to comment