Summary: | ASTERISK-21487: Stasis Core - Refactor Hold event from chan_sip/chan_iax2/sig_pri to channel core | ||
Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
Date Opened: | 2013-04-17 09:13:48 | Date Closed: | 2013-05-24 16:21:52 |
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: | {{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. | ||
Comments: |