[asterisk-bugs] [JIRA] (ASTERISK-29769) AMI call flow incorrect linkedId for transferred extension after AttendedTransfer event

[Joze Zivic (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-29769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joze Zivic updated ASTERISK-29769:
----------------------------------

    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.




  was:
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, 102 has correct linkedId:1.

Possibly, all transfer-kind events and all asterisk versions are affected by this bug.





> AMI call flow incorrect linkedId for transferred extension after AttendedTransfer event
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29769
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29769
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly., .Release/Targets
>    Affects Versions: 19.0.0
>            Reporter: Joze Zivic
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)