[Home]

Summary:ASTERISK-28351: CDR disposition incorrectly logged at file when AMD classifies as MACHINE
Reporter:Cirillo Ferreira (cirillor@lbv.org.br)Labels:
Date Opened:2019-03-26 10:02:15Date Closed:2020-01-14 11:14:01.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:CDR/General
Versions:13.18.5 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When the call is ended by AMD, the CDR logged at file Master.csv doen't contains the answer time and the disposition is FAILED, instead of ANSWERED.

Eg: Call to channel DAHDI/i12/0316334681296 which was answered by an answering machine, and classified as MACHINE by AMD in 4 sec.

Debug:
{noformat}
DEBUG[24310] cdr.c: Finalized CDR for DAHDI/i12/0316334681296-b5d8e - start 1553611364.871316 answer 1553611381.555625 end 1553611385.554073 dispo ANSWERED
{noformat}

CDR:
{noformat}
"","28604300","0111306334681296","from-sip","""Anonymous"" <28604300>","SIP/core-0095ea3a","DAHDI/i12/0316334681296-b5d8e","Dial","2019-03-26 11:42:44","","2019-03-26 11:43:05","20","0","FAILED","DOCUMENTATION","1553611364.28562544"
{noformat}

ps: Answer time is among start and end field. (10th field)

Probably the attribute "disposition" of cdr object is being overwritten before the CDR registration at file.
Comments:By: Asterisk Team (asteriskteam) 2019-03-26 10:02:16.016-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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Joshua C. Colp (jcolp) 2019-03-26 11:14:34.887-0500

It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists.

Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported.
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions


By: Joshua C. Colp (jcolp) 2019-03-26 11:15:02.745-0500

If after updating the problem still occurs then your CDR configuration file will also be needed.
By: Cirillo Ferreira (cirillor@lbv.org.br) 2019-03-26 14:17:20.330-0500

Ok Joshua,

I'll try update the version this week yet and do this test again.
By: Asterisk Team (asteriskteam) 2019-04-11 12:00:01.131-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines