[asterisk-bugs] [JIRA] (ASTERISK-24652) Confbridge interaction with CDR

[Jonathan White (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224477#comment-224477 ] 

Jonathan White commented on ASTERISK-24652:
-------------------------------------------

Thank you for the very detailed explanation, it is greatly appreciated.

We were simply expecting Asterisk to log individual calls from the time Asterisk answers to the time Asterisk hangs up on a per call basis.

Although we see the benefit of being able to track how calls interact with each other the fundamental use of CDR is log call start and call hang-up which in this instance (quite a common call scenario) Asterisk fails to provide, it's not even that clear what will be logged and when in different call scenarios.

At present we feel Asterisk is producing inaccurate and incomplete CDR records.

We can't see there is an option to capture the entire call duration in a single record. Is there an answer to this issue?

Thanks again for you kind support.

> Confbridge interaction with CDR
> -------------------------------
>
>                 Key: ASTERISK-24652
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24652
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_cdr, Applications/app_confbridge
>    Affects Versions: 13.0.2
>         Environment: centos6 i386
>            Reporter: Jonathan White
>            Assignee: Rusty Newton
>         Attachments: full, full
>
>
> I have noticed CDR is not reporting the correct duration for some calls.
> In my case I have calls being answered and a dialplan request for a pin before placing the caller into a confbridge.
> In some instances the duration of the call is reported to be the number of seconds before the call is placed into confbridge but none of the confbridge seconds are reported.
> If I put a second call into the same bridge the first call will report the correct call duration but the second call will report the duration of the call up to the point it is placed into the confbridge.
> My cdr config is simple. I am using CDR adaptive
> {noformat}
> [asterisk]
> connection=asterisk-odbc
> table=ast_cdr
> alias start => calldate
> {noformat}
> In addition I get a double entry for the CDR(userfield) I assume the combination of the two channels in the confbridge but this is only for the first call which enters the bridge not the second.
> Below is an example of the CDR output. The first line is the first call which shows the correct duration and billsec of 43 seconds. It also shows a double entry for CDR(userfield) Bridge-1005;Bridge-1005
> {noformat}
> "2014-12-28 02:31:00";"""2581"" <2581>";"2581";"1001";"apps";"SIP/2581-00000010";"SIP/2581-00000011";"ConfBridge";"1005,,user_admin,menu_admin";"43";"43";"ANSWERED";"3";;"1419733860.55";"Bridge-1005;Bridge-1005"
> {noformat}
> The second call only reports 18 seconds for billsec which is the amount of time the call lasts before being placed into the confbridge. This CDR record reports corectly the CDR(userfield) as Bridge-1005
> {noformat}
> "2014-12-28 02:31:22";"""2581"" <2581>";"2581";"1001";"apps";"SIP/2581-00000011";;"ConfBridge";"1005,,user_participant,menu_participant";"19";"18";"ANSWERED";"3";;"1419733882.59";"Bridge-1005"
> {noformat}
> My suspicion is there is an issue with how confbridge interacts with CDR



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