[asterisk-bugs] [JIRA] (ASTERISK-21495) 302 Moved Temporarily CDR Incorrect

[David Woolley (JIRA)]

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

David Woolley commented on ASTERISK-21495:
------------------------------------------

You should be using call event logging for all but the simplest of calls.  It was created because fixing one thing in CDRs kept breaking another.
                
> 302 Moved Temporarily CDR Incorrect
> -----------------------------------
>
>                 Key: ASTERISK-21495
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21495
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.21.0
>            Reporter: Ross Beer
>
> When a phone sends a 302 call forward, the CDRs contain the incorrect information.
> For example a call record for the diversion part of the CDR shows the duration, however the billsec is 0. This is incorrect as this part of the call is established and therefore the billsec should be shown.
> The cdr shows a call to 'Local/012412542554 at default-00000006;1', however I believe to resolve the issue the call needs to have the '/n' appended to the string before dialing. As this is in the chan_sip directly, this needs to be done in the source.
> Example CDR is:
> calldate,channel,dstchannel,duration,billsec
> 2013-04-17 18:35:49,SIP/<exten>-000dc1ee,Local/<mobile>@from-internal-00000007;1,55,40
> 2013-04-17 18:35:56,Local/<mobile>@from-internal-00000007;2,SIP/sipprvider-000dc1fb,8,0
> The second entry is the call to the mobile, however the call is bridged and the CDR added to the DB. However the call is still in progress. The call should not be bridged when answered, instead the two CDRs should continue until the call ends.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira