[asterisk-bugs] [JIRA] (ASTERISK-21488) Stasis Core - Refactor Registry events from chan_iax2/chan_sip
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Mon Apr 29 14:09:39 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan reassigned ASTERISK-21488:
--------------------------------------
Assignee: Jason Parker
> Stasis Core - Refactor Registry events from chan_iax2/chan_sip
> --------------------------------------------------------------
>
> Key: ASTERISK-21488
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21488
> Project: Asterisk
> Issue Type: New Feature
> Security Level: None
> Components: Channels/chan_iax2, Channels/chan_sip/General, Core/Channels, Core/Stasis
> Reporter: Matt Jordan
> Assignee: Jason Parker
> Labels: Asterisk12
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list