Ensure that presence state is decoded properly on Asterisk startup.
authorMark Michelson <mmichelson@digium.com>
Wed, 7 May 2014 21:58:37 +0000 (21:58 +0000)
committerMark Michelson <mmichelson@digium.com>
Wed, 7 May 2014 21:58:37 +0000 (21:58 +0000)
commit68066907e141757112cec3ef06711ee38fd88855
tree31ae264470d7a46c56c0e4d020d6a4defde2bd75
parenta92f0a9e83b6301ec2cbe754cf4fcfadf9079011
Ensure that presence state is decoded properly on Asterisk startup.

The CustomPresence provider callback will automatically base64 decode
stored data if the 'e' option was present when the state was set. However,
since the provider callback was bypassed on Asterisk startup, encoded
presence subtypes and messages were being sent instead. This fix makes
it so the provider callback is always used when providing presence
state updates.

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