[asterisk-bugs] [JIRA] (ASTERISK-22954) Incorrect treatment of amaflags, accountcode and userfield since ASTERISK-16990

[Steve Davies (JIRA)]

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

Steve Davies updated ASTERISK-22954:
------------------------------------

    Attachment: patches_1.8_10_11.diff

This is 3 patches in 1 file against version 1.8, 10 and 11 respectively. This patch is tested here using Asterisk 1.8 and seems to work fine.
                
> Incorrect treatment of amaflags, accountcode and userfield since ASTERISK-16990
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22954
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22954
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 1.8.24.0, 10.12.3, 11.6.0
>            Reporter: Steve Davies
>         Attachments: patches_1.8_10_11.diff
>
>
> During a blind transfer, or any other event that causes a channel masquerade, CDR records are swapped. The change made in ASTERISK-16990 (https://reviewboard.asterisk.org/r/1721/) does not take this into account.
> This results in the amaflags, accountcode and userfield data for a completely unrealted call leg being copied into a bridge_cdr, just before it is sent to the database :(
> It would almost be better if that patch had never been applied - Looking through the changelog, it has had a couple of knock on effects which are already patched.
> (Not sure if this applies to version 12 as the bridge code is so changed.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira