[asterisk-bugs] [JIRA] (ASTERISK-23741) CDR answer field takes value from previous field

[Grigoriy Puzankin (JIRA)]

Grigoriy Puzankin created ASTERISK-23741:
--------------------------------------------

             Summary: CDR answer field takes value from previous field
                 Key: ASTERISK-23741
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23741
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: CDR/cdr_adaptive_odbc
    Affects Versions: 11.9.0
         Environment: Gentoo Linux with the latest stable portage updates, kernel 3.12.13 x86_64, PostgreSQL 9.3.3, unixODBC 2.3.1.
            Reporter: Grigoriy Puzankin
            Severity: Minor


In some cases when a call was not answered the "answer" field may take timestamp value from "calldate", "end" or whatever was filled prior to "answer" field.

For example, create a CDR table, where three specific columns go in row "calldate", "answer" and "end" (create other fields according to documentation). Make call, but do not answer. Fetch your call from CDR table. The "answer" field should be empty, but it is filled with the same value as the "calldate" was filled.

If non-timestamp field goes prior to "answer", then the "answer" field will be empty, but there'll be a warning in logs about bad formatted date (with the value from previous column - WARNING[12951] cdr_adaptive_odbc.c: CDR variable callanswer is not a valid timestamp ('6209').).



--
This message was sent by Atlassian JIRA
(v6.2#6252)