Summary:	ASTERISK-29221: res_ari_bridges: improper error code when trying to delete a non-stasis bridge
Reporter:	Jean Aunis - Prescom (PrescomJA)	Labels:
Date Opened:	2020-12-22 06:25:24.000-0600	Date Closed:
Priority:	Minor	Regression?	No
Status:	Open/New	Components:	Resources/res_ari_bridges
Versions:	16.9.0	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:	( 0) full-delete-bridge-error.txt
Description:	When trying to delete a non-stasis bridge, a "500 Internal server error" response is generated. It seems Asterisk wants to generate a 409 response but the validation fails. For the sake of consistency, I think Asterisk should whether return a 409 error, or allow to destroy non-stasis bridges (since it is possible for channels).
Comments:	By: Asterisk Team (asteriskteam) 2020-12-22 06:25:25.528-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. 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) 2020-12-22 06:37:05.517-0600 According to the API documentation a 404 is the response code possible. For ARI it doesn't have a difference between a bridge created outside of itself and a bridge it doesn't know about. By: Joshua C. Colp (jcolp) 2020-12-22 06:37:41.463-0600 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Jean Aunis - Prescom (PrescomJA) 2020-12-22 06:52:10.576-0600 The error is at lines 1205 - 1206. By: Joshua C. Colp (jcolp) 2020-12-22 07:06:51.749-0600 Validation itself only occurs in dev mode, so on non-dev mode this would likely actually send the 409.