[asterisk-bugs] [JIRA] (ASTERISK-19407) Set CDR variable ignored on record created after after ForkCDR

[Frederic Van Espen (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200906#comment-200906 ] 

Frederic Van Espen commented on ASTERISK-19407:
-----------------------------------------------

We are encountering this issue as well on the latest release of asterisk: 1.8.19.0
                
> Set CDR variable ignored on record created after after ForkCDR
> --------------------------------------------------------------
>
>                 Key: ASTERISK-19407
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19407
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_cdr
>    Affects Versions: 1.8.9.2
>         Environment: RHEL 6.2
>            Reporter: Private Name
>         Attachments: asterisk-bug.txt
>
>
> I added some extra fields to my CDR table, and it does work when Asterisk starts, for instance , If I do a "Set(CDR(myfield)=XX)", and then I do a ResetCDR(w), it does insert the extra information correctly. However, if I do ForkCDR(e), then  any "Set(CDR(myfield)=XX)" followed by ResetCDR(w) after that will ignore the extra fields to the table. This is wrong, since we need a new record, but using with the current table definition.
> This happens regarding the driver used. I tested with cdr_odbc, cdr_mysql and cdr_adaptive_odbc. So it is a core issue. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira