Remove inconsistency in CEL eventtype for user defined events.
authorRichard Mudgett <rmudgett@digium.com>
Wed, 1 Feb 2012 17:42:15 +0000 (17:42 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Wed, 1 Feb 2012 17:42:15 +0000 (17:42 +0000)
commit797d633139a52a87736c04b71e31b1cb66e21e08
treeed8848795a995d9e2986bdd30a867d1a8f3b7044
parenta99b3c817baf50cf4edc70e991c0395c3d6d0311
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
cel/cel_manager.c
cel/cel_odbc.c
cel/cel_pgsql.c
cel/cel_tds.c
configs/cel.conf.sample
configs/cel_custom.conf.sample
configs/cel_odbc.conf.sample
configs/cel_pgsql.conf.sample
configs/cel_sqlite3_custom.conf.sample
main/cel.c