Summary:	ASTERISK-29409: ARI / endpoint subscription : FRACK when removing an endpoint
Reporter:	Jean Aunis - Prescom (PrescomJA)	Labels:
Date Opened:	2021-04-29 04:47:54	Date Closed:	2021-04-29 05:26:59
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_ari_applications
Versions:	16.16.2	Frequency of Occurrence	Constant
Related Issues:	duplicates ASTERISK-28237 "FRACK!, Failed assertion bad magic number" happens when unsubscribe an application from an event source
Environment:		Attachments:	( 0) full.log ( 1) refs.log ( 2) sip.conf ( 3) test-ari.js
Description:	Perform two subscriptions with ARI: - a subscription to a specific endpoint (endpoint:SIP/test) - a subscription to the associated technology (endpoint:SIP) When the endpoint is deleted in the configuration, a FRACK occurs. This issue is reproduced with chan_sip and chan_iax2 endpoints. It does not happen with PJSIP endpoints. It looks like PJSIP endpoints are not actually removed from Asterisk when removed from the configuration, they are merely considered as "unreachable". Steps to reproduce: - declare a peer in sip.conf - subscribe to this peer and to the SIP technology with ARI - remove the peer from sip.conf and execute "sip reload" Please find attached: - a NodeJS file performing the subscriptions - the sip.conf file declaring the peer - log "full" with debug level 5 - AO2 reference debugging
Comments:	By: Asterisk Team (asteriskteam) 2021-04-29 04:47:55.824-0500 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) 2021-04-29 04:56:02.835-0500 There is currently a patch up[1] for dealing with unsubscribes and FRACKs. Does this alter the result? [1] https://gerrit.asterisk.org/c/asterisk/+/15762 By: Jean Aunis - Prescom (PrescomJA) 2021-04-29 05:04:47.905-0500 It does! No FRACK anymore.