[Asterisk-bugs] [Asterisk 0010067]: CDR dst and dcontext field wrong information depending if caller or callee hangs up first

[noreply at bugs.diguim.com]

email_notification_title_for_action_bugnote_submitted 
====================================================================== 
http://bugs.digium.com/view.php?id=10067 
====================================================================== 
Reported By:                samdell3
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   10067
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.5 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
====================================================================== 
Date Submitted:             06-26-2007 17:49 CDT
Last Modified:              06-29-2007 10:09 CDT
====================================================================== 
Summary:                    CDR dst and dcontext field wrong information
depending if caller or callee hangs up first
Description: 
We are in the process of bench testing 1.4.5 (gotta love that T.38!)
This bug can be replicated 100% of the time.
I classify this as major as many calls cannot be billed.

All test calls are SIP to SIP. Caller = 6500011,  Callee = 6500012

If the CALLER hangs up first: 
CDR record logs dst and dcontext field from within the macro. Weird. EG
dst field results in 's' and dcontext results in 'macro-call-sip-nap'

If the CALLEE hangs up first:
CDR is recorded OK
dst field results in '66500012' and dcontext results in 'default'

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

---------------------------------------------------------------------- 
 cstadlmann - 06-29-07 10:09  
---------------------------------------------------------------------- 
tracinet - If you look at the bugtracker often, you will see that 1.4.4 had
several bugs which are fixed in 1.4.5.
Because I don't want to wait that long time for a new release version I
use svn-branch in my production system. You can grab a 'fresh' copy every
week or so, and major bugs are fixed.
Going back to 1.4.4 is nothing I would recommend. Lastest svn-branch
version runs very smooth on my system, expect for that nasty cdr issue.
But... The workaround works for me, and maybe murf can spend some time
fixing the bug. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-29-07 10:09  cstadlmann     Note Added: 0065916                          
======================================================================