[asterisk-bugs] [JIRA] (ASTERISK-21124) cdr_adaptative_odbc does not populate cdr information

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-21124:
-----------------------------------

    Assignee: Matt Jordan  (was: allan ananian)
      Status: Triage  (was: Waiting for Feedback)
    
> cdr_adaptative_odbc does not populate cdr information
> -----------------------------------------------------
>
>                 Key: ASTERISK-21124
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21124
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_adaptive_odbc
>    Affects Versions: 1.8.20.1
>         Environment: Centos 6.2 , Kernel 2.6.32-220, MySQL Server 5.1, UnixODBC
>            Reporter: allan ananian
>            Assignee: Matt Jordan
>         Attachments: full.log
>
>
> After I upgraded my version asterisk "1.8.16.0"  to "1.8.20.1" CDR_ADAPTATIVE_ODBC stopped writin.
> Example:
> {noformat}
> ; cdr_adaptive_odbc.conf
> [adaptive_connection]
> connection=asterisk
> table=cdr
> {noformat}
> {noformat}
> *CLI> cdr show status
> Call Detail Record (CDR) settings
> ----------------------------------
>   Logging:                    Enabled
>   Mode:                       Simple
>   Log unanswered calls:       No
> * Registered Backends
>   -------------------
>     cdr-syslog
>     Adaptive ODBC
>     cdr-custom
>     csv
>     cdr_manager
> {noformat}
> {noformat}
> exten => _NXXNXXXXXX,1,Verbose(1,Example of adaptive ODBC usage)
>    same => n,Set(CDR(route_rate)=0.01)
>    same => n,Dial(SIP/my_itsp/${EXTEN})
>    same => n,Hangup()
> {noformat}
> {noformat}
> | src          | duration | billsec | route_rate |
> | 0000FFFF0008 | 37       | 30      |            | 
>  
> {noformat}
> I put back asterisk "1.8.16.0" and came back to work just fine.
> Thanks.

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