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

[Joshua Colp (JIRA)]

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

Joshua Colp closed ASTERISK-22954.
----------------------------------

    Resolution: Suspended

CDRs were majorly rewritten as a result of work done in Asterisk 12 and Asterisk 13. We no longer swap records and such things.

If this issue is still applicable, though, feel free to comment and it will automatically reopen.

> [patch] 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 was sent by Atlassian JIRA
(v6.2#6252)