[asterisk-bugs] [JIRA] (ASTERISK-21487) Stasis Core - Refactor Hold event from chan_sip/chan_iax2/sig_pri to channel core

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21487:
-----------------------------------

    Summary: Stasis Core - Refactor Hold event from chan_sip/chan_iax2/sig_pri to channel core  (was: Stasis Core - Refactor Hold event from chan_sip/chan_iax2 to channel core)
    
> Stasis Core - Refactor Hold event from chan_sip/chan_iax2/sig_pri to channel core
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21487
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21487
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_iax2, Channels/chan_sip/General, Core/Channels, Core/Stasis
>            Reporter: Matt Jordan
>
> {{chan_sip}}, {{chan_iax2}}, and {{sig_pri}} raise a Hold event when the channel is put on hold. In both cases, however, an {{AST_CONTROL_HOLD}}/{{AST_CONTROL_UNHOLD}} frame is queued up on the channel.
> These events are better served in the Asterisk core. This way, a channel being put on hold/taken off hold has a stasis message relayed for it for all channel drivers, as opposed to IAX2/SIP specifically.
> The Hold/Unhold message should be a channel snapshot or - alternatively - a channel handle as the channel state itself doesn't change. JSON can convey the musicclass.
> Note that this should be a Hold/Unhold event in AMI.

--
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