Summary:	ASTERISK-21103: Stasis Core - Refactor the other event types onto the Stasis Core message bus
Reporter:	Matt Jordan (mjordan)	Labels:	Asterisk12
Date Opened:	2013-02-14 16:38:53.000-0600	Date Closed:	2013-05-17 12:38:46
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/Stasis
Versions:		Frequency of Occurrence
Related Issues:	cannot be resolved before completion of ASTERISK-20959 Create Stasis Core Module is related to ASTERISK-21460 New SIP Channel Driver - create a SIP Security Event module suitable for consumption in the new SIP stack
Environment:		Attachments:
Description:	Once the Stasis Core API is finished, we need to begin refactoring current consumers/producers on the event subsystem to take advantage of it. Other issues cover the 'first class' object types; this issue is to take care of: * {{-AST_EVENT_NETWORK_CHANGE-}} * {{-AST_EVENT_SECURITY-}} * {{-AST_EVENT_ACL_CHANGE-}} There is a good chance that the appropriate message payload for these event types will be a JSON message that contains the information about how the item changed.
Comments: