Summary:	ASTERISK-21488: Stasis Core - Refactor Registry events from chan_iax2/chan_sip
Reporter:	Matt Jordan (mjordan)	Labels:	Asterisk12
Date Opened:	2013-04-17 09:19:47	Date Closed:	2013-07-08 09:43:08
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_iax2 Channels/chan_sip/General Core/Channels Core/Stasis
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Both {{chan_sip}} and {{chan_iax2}} raise a Registry event. This does not cleanly map to a channel (it doesn't exist yet), or a device (there may not be one). It *may* map to the concept of an endpoint. If so, the Stasis-Core message should reference the appropriate endpoint. The fields between IAX2 and SIP should be standardized as much as possible. JSON can be used to convey them, but a routine in manager will have to be careful as it extracts the fields and know which ones are optional. Additionally, the registration modules for {{chan_gulp}} will need to have the Stasis-Core messages added to them.
Comments: