Make behavior of the PRESENCE_STATE 'e' option more consistent.
authorMark Michelson <mmichelson@digium.com>
Thu, 1 May 2014 16:21:09 +0000 (16:21 +0000)
committerMark Michelson <mmichelson@digium.com>
Thu, 1 May 2014 16:21:09 +0000 (16:21 +0000)
commit120ac66df9021a122d6a7cb492002a685c137403
tree00f6feecd32be373bd736368ab40246a35e70a60
parentfc4c5ca3deecd8b5cb0063e58e9d49b43acc065b
Make behavior of the PRESENCE_STATE 'e' option more consistent.

When writing presence state, if 'e' is specified, then the presence state will
be stored in the astdb encoded. However, consumers of presence state events or those
that query for the presence state will be given decoded information. If base64 encoding
is desired for consumers, then the information can be base64-encoded manually and the
'e' option can be omitted.

closes issue ASTERISK-23671
Reported by Mark Michelson

Review: https://reviewboard.asterisk.org/r/3482

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@413183 65c4cc65-6c06-0410-ace0-fbb531ad65f3
funcs/func_presencestate.c