Summary: | ASTERISK-28141: mysql same value calldate,answer,end | ||
Reporter: | Mesut Altürk (multimesut) | Labels: | |
Date Opened: | 2018-10-31 01:26:01 | Date Closed: | 2018-11-01 07:41:36 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Addons/app_mysql |
Versions: | 13.23.1 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Attachments: | ( 0) debug_log_123456_ok.txt ( 1) Ekran_Alıntısı.JPG ( 2) Ekran_Alıntısı2.JPG | |
Description: | We have updated asterisk version from 13.2.0 to 13.23.1. Currently "answer" and "end" areas on cdr table in MySQL is same with "calldate". Same values are written to these areas. Is there any change about that in new version? | ||
Comments: | By: Asterisk Team (asteriskteam) 2018-10-31 01:26:02.177-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: George Joseph (gjoseph) 2018-10-31 10:20:50.752-0500 You have a lot going on in your dialplan! Can you try a two party call with a simple dialplan that just does a Dial() to the second party and look at the CDR? Do you still have the issue? By: Mesut Altürk (multimesut) 2018-11-01 01:48:35.569-0500 Yes, the problem continues. I've added a new picture. And I did the following. I called directly without any rules. There was no problem in asterisk 13.2.0. [DLPN_DialPlan1] exten = 100,1,Dial(SIP/100) By: George Joseph (gjoseph) 2018-11-01 07:41:37.050-0500 I was able to reproduce your issue but only using the cdr_mysql module that has been deprecated for several years. The only currently supported CDR module for MySql is the cdr_adaptive_odbc module and that one does insert the correct times into the table. You should upgrade to that module. |