Summary:	ASTERISK-30504: Support sending in-dialog messages to channel via ARI
Reporter:	Joe Searle (jsearle)	Labels:
Date Opened:	2023-04-26 03:50:08	Date Closed:
Priority:	Minor	Regression?	No
Status:	Triage/New	Components:	Resources/res_ari_channels
Versions:	GIT 20.2.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I would like to propose adding support for sending in-dialog messages via the ARI on the channel route. This would allow ARI applications to exchange information with SIP clients in the same way that Confbridge does with its 'Enhanced Messaging' events. https://www.asterisk.org/enrich-your-conference-app-with-asterisk-enhanced-messaging-part-2/ I imagine this would take the form (or similar) POST /channels/{channelId}/send_message I initially raised this in the community forums here: https://community.asterisk.org/t/ari-in-dialog-messages-confbridge-enhanced-messaging/96677 My particular use case for this would be using a ARI application to replace Confbridge where the new functionality would allow me to emulate the ConfbridgeWelcome, ConfbridgeJoin & ConfbridgeLeave events.
Comments:	By: Asterisk Team (asteriskteam) 2023-04-26 03:50:12.582-0500 WARNING JIRA will be going read-only at the end of April, 2023. We will be starting fresh on Github at https://github.com/asterisk/asterisk at that time. No issues or patches will be copied to Github. If you file an issue on JIRA at this time you will need to recreate it on Github after this date. The same applies if you have a patch. WARNING Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2023-04-26 03:55:17.517-0500 It should be "message" and not "send_message". The POST implies it is sending. Are you planning to do this work? We don't accept feature requests on the issue tracker, and in a few days we will be moving to Github regardless. By: Joe Searle (jsearle) 2023-04-26 09:22:10.251-0500 I don't think my C skills are up to adding this myself but I might have to make an attempt if there isn't any interest from actual C developers. Is there a better place to log feature requests currently? Will feature requests be accepted in github issues? By: Joshua C. Colp (jcolp) 2023-04-26 09:27:17.154-0500 There's no real centralized place for logging feature requests. Feature requests won't be accepted in Github issues. Policy isn't changing as of this point. Our goal is to get on Github first, and then such things can be revisited afterwards.