Summary:	ASTERISK-29958: app_dial: Hangup cause disappears if progress received
Reporter:	N A (InterLinked)	Labels:
Date Opened:	2022-03-08 05:28:16.000-0600	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Applications/app_dial
Versions:	18.9.0	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:	( 0) ASTERISK-29958.txt
Description:	There seems to be a bug whereby if Progress is received during the call, then the hang up cause disappears when the Dial returns. This makes it impossible to determine the actual disposition of the call, and whether it succeeded or not, since the hangup cause code has disappeared. Hanging up manually with cause code 3 BEFORE Progress works correctly, and AFTER Progress, does not work correctly anymore. {noformat} GOOD CALL: [2022-03-08 11:21:45]     -- Executing [WATSRC@wats:1] Goto("Local/WATSRC@wats-000000c2;2", "out-pjsip,REDACTED,1") in new stack [2022-03-08 11:21:45]     -- Goto (out-pjsip,REDACTED,1) [2022-03-08 11:21:45]     -- Executing [REDACTED@out-pjsip:1] Hangup("Local/WATSRC@wats-000000c2;2", "3") in new stack [2022-03-08 11:21:45]   == Spawn extension (out-pjsip, REDACTED, 1) exited non-zero on 'Local/WATSRC@wats-000000c2;2' [2022-03-08 11:21:45]   == Everyone is busy/congested at this time (1:0/0/1) [2022-03-08 11:21:45]     -- Executing [WATSRC@trunk-access:10] NoOp("Local/wats@REDACTED-originate-local-000000c1;2", "3: CHANUNAVAIL") in new stack [2022-03-08 11:21:45]     -- Executing [WATSRC@trunk-access:11] Set("Local/wats@REDACTED-originate-local-000000c1;2", "CALLERID(name)=InterLinked") in new stack [2022-03-08 11:21:45]     -- Executing [WATSRC@trunk-access:12] Goto("Local/wats@REDACTED-originate-local-000000c1;2", "done,1") in new stack [out-pjsip] ; EXTEN = peer name exten => _[A-Za-z].,1,Set(CDR_PROP(disable)=1) same => n,Hangup(3) same => n,Progress() FAIL!: [2022-03-08 11:23:02]     -- Executing [WATSRC@wats:1] Goto("Local/WATSRC@wats-000000cc;2", "out-pjsip,REDACTED,1") in new stack [2022-03-08 11:23:02]     -- Goto (out-pjsip,REDACTED,1) [2022-03-08 11:23:02]     -- Executing [REDACTED@out-pjsip:1] Set("Local/WATSRC@wats-000000cc;2", "CDR_PROP(disable)=1") in new stack [2022-03-08 11:23:02]     -- Executing [REDACTED@out-pjsip:2] Progress("Local/WATSRC@wats-000000cc;2", "") in new stack [2022-03-08 11:23:02]     -- Local/WATSRC@wats-000000cc;1 is making progress passing it to Local/wats@REDACTED-originate-local-000000cb;2 [2022-03-08 11:23:02]     -- Sending DTMF 'WW1wats' to the called party as result of receiving a PROGRESS message. [2022-03-08 11:23:02]     -- Local/815614342218@REDACTED-originate-local-000000cb;1 is making progress passing it to Local/PJSIPATAxGrandstream2@REDACTED-outgoing-000000c9;1 [2022-03-08 11:23:02]     -- Executing [REDACTED@out-pjsip:3] Hangup("Local/WATSRC@wats-000000cc;2", "3") in new stack [2022-03-08 11:23:02]   == Spawn extension (out-pjsip, REDACTED, 3) exited non-zero on 'Local/WATSRC@wats-000000cc;2' [2022-03-08 11:23:02] WARNING[22437][C-00000052]: app_dial.c:1856 wait_for_answer: Unable to forward frametype: 2 [2022-03-08 11:23:02]     -- Executing [WATSRC@trunk-access:10] NoOp("Local/wats@REDACTED-originate-local-000000cb;2", "0: NOANSWER") in new stack [out-pjsip] ; EXTEN = peer name exten => _[A-Za-z].,1,Set(CDR_PROP(disable)=1) same => n,Progress() same => n,Hangup(3) {noformat}
Comments:	By: Asterisk Team (asteriskteam) 2022-03-08 05:28:18.790-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) 2022-03-08 05:34:54.406-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: N A (InterLinked) 2022-03-08 05:44:52.252-0600 As requested, a debug with level 5. By: N A (InterLinked) 2022-03-08 06:48:00.139-0600 Just as a clarification, what exactly does it mean when there is a Digium internal issue linked to an Asterisk issue? I see these on some issues, but not all of them. Does it mean that Sangoma is working on the issue? Does it mean that Sangoma may potentially work on the issue at some point? Does it mean Sangoma considers the issue "important" enough to have an internal copy? Or does it not really mean anything much? Just logistically speaking, trying to figure out what impact this has, if any, such as if there is information there that is missing here. Thanks! By: Joshua C. Colp (jcolp) 2022-03-08 06:51:13.016-0600 It means that it's been triaged, is something supported by Sangoma, and is in queue. It doesn't mean it's being worked on or that there is any time frame.