Summary:	ASTERISK-28227: Adding more ARI subscription type
Reporter:	sungtae kim (pchero)	Labels:
Date Opened:	2018-12-31 03:48:17.000-0600	Date Closed:	2018-12-31 05:34:53.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_ari
Versions:	16.1.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Hi, Asterisk team, I'm thinking about adding the new feature for the Asterisk. It's "Adding Resource item for subscription". Purpose: Currently, the ARI subscription supports 3 types of subscriptions. Channels, Bridges, Endpoints. It's a good enough to see and check to what/how/where the channels is going. But using the ARI, it's not an easy to check the resource(module)s. Simply, the ARI does not support module's notification message sending and receiving. I would like to add the 1 more subscription type which is "Resources". This feature is designed for sending/receiving the module's notification messages. AS-IS {noformat} asterisk*CLI> ari show app pchero_voip Name: pchero_voip  Debug: No  Subscription Model: Global Resource Subscription  Subscriptions: 3    Channels:      __AST_CHANNEL_ALL_TOPIC (1)    Bridges:      __AST_BRIDGE_ALL_TOPIC (1)    Endpoints:      __AST_ENDPOINT_ALL_TOPIC (1) {noformat} TO-BE {noformat} asterisk*CLI> ari show app pchero_voip Name: pchero_voip  Debug: No  Subscription Model: Global Resource Subscription  Subscriptions: 4    Channels:      __AST_CHANNEL_ALL_TOPIC (1)    Bridges:      __AST_BRIDGE_ALL_TOPIC (1)    Endpoints:      __AST_ENDPOINT_ALL_TOPIC (1)    Resources:      __AST_RESOURCE_ALL_TOPIC (1) {noformat} Resources: Resources items would be the name of each modules. By subscribing the modules, it will receive the each modules's event/notification ARI messages. For example, if the ARI application subscribing the app_queue resource, the application will be received below ARI events. QueueCallerJoin, QueueCallerAbandon, ... So, is this feature would be worth for the Asterisk? If it's not a bad idea, I would like to start it. :)
Comments:	By: Asterisk Team (asteriskteam) 2018-12-31 03:48:19.665-0600 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. 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]. By: Joshua C. Colp (jcolp) 2018-12-31 05:34:53.278-0600 Please use the asterisk-dev mailing list[1] for this type of discussion, as people in the community don't generally monitor every issue and this would get lost and not represent what people think. As well there is a discussion about ARI event filtering going on[2] which this is related to. [1] http://lists.digium.com/mailman/listinfo/asterisk-dev [2] http://lists.digium.com/pipermail/asterisk-dev/2018-December/077128.html By: sungtae kim (pchero) 2018-12-31 06:16:31.460-0600 Thanks!! :) By: Asterisk Team (asteriskteam) 2018-12-31 06:16:31.642-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.