Summary:	ASTERISK-29106: Survey after Hangup
Reporter:	Jliuk (Jliuk)	Labels:
Date Opened:	2020-10-05 07:12:32	Date Closed:	2020-10-05 08:02:35
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Core/PBX
Versions:	16.11.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Hello, I'm new to Asterisk and I'm having trouble to manage an IVR for a survey after the hang up. I have Asterisk 16.11.1 and FreePBX 15.0.16.75. I managed to let it work when I set it as custom destination from FreePBX, but now I would like the following instructions to be executed when an operator hangs up: [macro-survey] exten => s,1,answer() ;this asks the first question (based on your recording) and stores them in variable exten => s,n(question1),Read(answer1,enter-ext-of-person,1,,1,2) exten => s,n,GotoIf($[ ${answer1} < 4 ]?question2:question1) ;this asks the first question (based on your recording) and stores them in variable exten => s,n(question2),Read(answer2,enter-ext-of-person,1,,1,2) exten => s,n,GotoIf($[ ${answer2} < 4 ]?finish:question1) ;this line puts the two answers together and separates them with a | symbol. exten => s,n(finish),set(answer=${answer1}|${answer2}) ;this saves the answers into the CDR field of "userfield" exten => s,n,Set(CDR(userfield)=${answer}) exten => s,n,hangup() This context is saved into /etc/asterisk/extensions_override_freepbx.conf that should override the /etc/asterisk/extensions_additional.conf behaviour. I've tried to put the following into the [ext-local] dialplan: exten => s,n,Set(CHANNEL(hangup_handler_push)=macro-survey,s,1); or exten => h,1,Goto(macro-survey,s,1) But it doesn't seem to work. Can you help me? Thank you.
Comments:	By: Asterisk Team (asteriskteam) 2020-10-05 07:12:33.050-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: Asterisk Team (asteriskteam) 2020-10-05 07:12:33.418-0500 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2020-10-05 07:13:22.920-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Asterisk Team (asteriskteam) 2020-10-05 07:45:48.309-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.