[asterisk-bugs] [JIRA] Issue Comment Edited: (ASTERISK-20351) SIP attended transfer - wrong billsec in CDR (transferring side)

[Maciej Krajewski (JIRA)]

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

Maciej Krajewski edited comment on ASTERISK-20351 at 9/3/12 7:15 AM:
---------------------------------------------------------------------

Well, actually I would not agree that basic CDR transfer (AT) is a complex scenario. If the second CDR has the time of B-C Call + A-C everything would be ok.

      was (Author: jamicque):
    Well, actually I would not agree that basic CDR transfer (AT) is a complex scenario.
  
> SIP attended transfer - wrong billsec in CDR (transferring side)
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-20351
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20351
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 1.8.15.0
>            Reporter: Maciej Krajewski
>            Severity: Critical
>         Attachments: full.gz
>
>
> There is a serious problem with bill sec in Attended transfer scenario.
> Scenario:
> A is calling do B
> B puts A on HOLD
> B calls to C
> B makes transfer C with A
> After such scenario asterisk by default make 2 CDR's:
> 1) the whole A call with the duration of the call A-B + HOLD + A-C (and this is all right)
> 2) B-C billsec shows only the time with B-C call and no time after the transfer - this is a crucial mistake especially if you would like to charge the B for the transfer (there is no way of doing that).
> If tried different configuration and using ForkCDR and ResetCDR in dialplan. However, none of them can give me the time A and C where actually talking.
> IMHO the billsec of the second CDR should have the time of B-C call + A-C
> here is my dialplan (I've attached the proper logs)
> {code}
> exten => h,1,NoOp()
> exten => h,2,Hangup
> exten => 2,1,Dial(SIP/test002)
> same => n,Hangup()
> exten => 3,1,Dial(SIP/test003)
> same => n,Hangup()
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira