[asterisk-bugs] [JIRA] (ASTERISK-22613) cdr_prop function is not working

[Private Name (JIRA)]

Private Name created ASTERISK-22613:
---------------------------------------

             Summary: cdr_prop function is not working
                 Key: ASTERISK-22613
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22613
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Functions/func_cdr
    Affects Versions: 12.0.0-alpha1
         Environment: debian 7 
            Reporter: Private Name


In this function, the "cmd" variable has the wrong content when I execute set(CDR_PROP(disable)=true)
I always get the error "Unknown option CDR_PROP", so I set a warning before, and in fact, the cmd variable contains "CDR_PROP" when it should contain "disable"
{
        enum ast_cdr_options option;
        if (!strcasecmp("party_a", cmd)) {
                option = AST_CDR_FLAG_PARTY_A;
        } else if (!strcasecmp("disable", cmd)) {
                option = AST_CDR_FLAG_DISABLE_ALL;
        } else {
                ast_log(AST_LOG_WARNING, "Unknown option %s used with CDR_PROP\n", cmd);
                return 0;

This is part of larger issue. I have simple call-in and call-out scenario, with channel PJSIP. For some reason, I think by design, I get a second CDR record, completely wrong and unnecessary. In this unwanted record, most fields are empty and the duration and billsec do not match the "correct" record.
So I am trying to disable the "party_B" cdr. 
In general, how do I get the right CDR in this dialplan.
(Two lines).

exten=> _X.,1,Dial(PJSIP/ENDPOINT/sip:${EXTEN}@X.Y.Z.T)
exten=> _X.,n,Hangup()





 

--
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