[asterisk-bugs] [Asterisk 0012943]: SIP Channel Reports Wrong CDR

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12943 
====================================================================== 
Reported By:                visu
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   12943
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-06-28 08:42 CDT
Last Modified:              2008-08-06 09:49 CDT
====================================================================== 
Summary:                    SIP Channel Reports Wrong CDR
Description: 
SIP Channel always reports wrong CDR in following case

We have following setup where Internal Clients connects to external world
using Asterisk

[Internal Clients] -------- [Asterisk] --------- [External World]

When internal clients dial external number, Asterisk dials outside number
and everything works great. However, Asterisk always reports CDR 8 even if
caller party drops the call before called party picks up. The call time
reported is duration of calling party

If called party does not pickup the phone, CDR is also 8 but this time
duration is 0






====================================================================== 

---------------------------------------------------------------------- 
 (0091143) murf (administrator) - 2008-08-06 09:49
 http://bugs.digium.com/view.php?id=12943#c91143 
---------------------------------------------------------------------- 
I am going to need more information to reproduce and fix this bug,
whatever
it is. I don't understand what "CDR 8" is, where it occurs, or why.

So, show me example output; perhaps the output if cdr-custom is used, of a
CDR that is bad, and the Dial command that you used which generated the bad
CDR,
and the devices (all SIP?) that were involved in making the call with the
bad CDR.
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-06 09:49 murf           Note Added: 0091143                          
======================================================================