Summary:	ASTERISK-29769: AMI call flow incorrect linkedId for transferred extension after AttendedTransfer event
Reporter:	Joze Zivic (jozza)	Labels:
Date Opened:	2021-11-22 07:07:03.000-0600	Date Closed:	2021-12-07 12:00:00.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	. I did not set the category correctly. .Release/Targets
Versions:	19.0.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Example: 100 calls 101 (linkedId: 1), 101 answers, then 101 makes a consultation call to 102 (linkedId: 2), then 101 transfers the call to 102, before 102 answers. When 102 answers,  NewState:Up event for 102 has linkedId:2 instead of linkedId: 1. When call is disconnected (Hangup) for 102, it has correct linkedId:1. Possibly, all transfer-kind events and all asterisk versions are affected by this bug.
Comments:	By: Asterisk Team (asteriskteam) 2021-11-22 07:07:05.154-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: Kevin Harwell (kharwell) 2021-11-23 11:31:42.403-0600 What channel driver are you using? Please attach the Asterisk log with the appropriate channel driver's message (SIP?) trace enabled. Also, include and/or attach the AMI output from the described scenario. Thanks! By: Asterisk Team (asteriskteam) 2021-12-07 12:00:00.617-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines