[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 03:43 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'

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

---------------------------------------------------------------------- 
 samdell3 - 06-29-07 03:43  
---------------------------------------------------------------------- 
cstadlmann, Thanks for your workaround. I might give that a go. We also use
MySQL. Otherwise plan-b is to write a perl script to read the (incorrect)
records and update the wrong dst fields based on the 'lastdata' field. In
our case, it will look something like
'SIP/5551068781269#@imgnap1|60|L(14400000)' therefore we can extract the
dst number as 68781269. 

Really messy, and not exactly a workaround, but I have ZERO experience
with C coding... however, I might grab myself a copy of "C for dummies" and
begin trawling. As a starting point, may I ask where this bug *could* lie?
EG would it be a simple as a bug in cdr.c, or is this a lot deeper and tied
into a lot of other code/variables ? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-29-07 03:43  samdell3       Note Added: 0065892                          
======================================================================