ARI: Don't leak implementation details
authorKinsey Moore <kmoore@digium.com>
Fri, 22 Nov 2013 20:10:46 +0000 (20:10 +0000)
committerKinsey Moore <kmoore@digium.com>
Fri, 22 Nov 2013 20:10:46 +0000 (20:10 +0000)
commitd9015a5356dfff70ce15ed2ea5726325de71d9e3
treeb4b253dcc96a4cbc27f54ee294dae45264e12dbb
parent1c45a32ee861fa427e0243abe03c729966fa4436
ARI: Don't leak implementation details

This change prevents channels used as implementation details from
leaking out to ARI. It does this by preventing creation of JSON blobs
of channel snapshots created from those channels and sanitizing JSON
blobs of bridge snapshots as they are created. This introduces a
framework for excluding information from output targeted at Stasis
applications on a consumer-by-consumer basis using channel sanitization
callbacks which could be extended to bridges or endpoints if necessary.

This prevents unhelpful error messages from being generated by
ast_json_pack.

This also corrects a bug where BridgeCreated events would not be
created.

(closes issue ASTERISK-22744)
Review: https://reviewboard.asterisk.org/r/2987/
Reported by: David M. Lee
........

Merged revisions 403069 from http://svn.asterisk.org/svn/asterisk/branches/12

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@403070 65c4cc65-6c06-0410-ace0-fbb531ad65f3
16 files changed:
include/asterisk/stasis.h
include/asterisk/stasis_app.h
include/asterisk/stasis_bridges.h
include/asterisk/stasis_channels.h
include/asterisk/stasis_endpoints.h
main/json.c
main/rtp_engine.c
main/stasis_bridges.c
main/stasis_channels.c
main/stasis_endpoints.c
main/stasis_message.c
res/ari/resource_bridges.c
res/ari/resource_channels.c
res/ari/resource_endpoints.c
res/res_stasis.c
res/stasis/app.c