Summary:	ASTERISK-28266: Added ARI resource /ari/aserisk/ping
Reporter:	sungtae kim (pchero)	Labels:
Date Opened:	2019-01-28 17:22:12.000-0600	Date Closed:	2019-02-14 04:37:42.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_ari
Versions:	16.1.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Added ARI resource for ping. It returns "pong" message with timestamp and asterisk_id. {noformat} $ curl -X GET -u asterisk:asterisk localhost:8088/ari/asterisk/ping | python -m json.tool  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                 Dload  Upload   Total   Spent    Left  Speed 100    92  100    92    0     0  10554      0 --:--:-- --:--:-- --:--:-- 11500 {    "asterisk_id": "00:11:22:33:44:55",    "ping": "pong",    "timestamp": "2019-01-29T00:17:41.059+0100" } {noformat}
Comments:	By: Asterisk Team (asteriskteam) 2019-01-28 17:22:12.615-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]. 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. By: sungtae kim (pchero) 2019-02-14 02:41:09.408-0600 Already merged into Asterisk-13, 16 and master. By: sungtae kim (pchero) 2019-02-14 02:42:41.243-0600 I'm not clear what the status should be for next. :P It's been integrated into Asterisk-13, 16 and master. But not released it yet. Please update the ticket's status if someone knows what status should be. By: Richard Mudgett (rmudgett) 2019-02-14 10:19:02.368-0600 Automation did not automatically close the issue because you did not put the JIRA issue id in the commit message.  This is something we'll have to be more proactive against as it will also cause the issue target release versions to not be automatically updated by the release scripts when the fix makes its way into an Asterisk release. In the future please make sure you have the JIRA issue id in the commit message as it cannot be corrected after the patch is merged. By: sungtae kim (pchero) 2019-02-14 10:48:59.209-0600 Now I've got it. I will keep in mind that. Sorry! :) By: Asterisk Team (asteriskteam) 2019-02-14 10:48:59.548-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.