[asterisk-bugs] [Asterisk 0016026]: cdr blind transfer problem

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16026 
====================================================================== 
Reported By:                foxfire
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16026
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-06 10:44 CDT
Last Modified:              2009-10-06 12:21 CDT
====================================================================== 
Summary:                    cdr blind transfer problem
Description: 
When performing a Blind transfer on a phone of an incoming phone call, and
transfering it before the called party answers will mess up the CDR
records.
CDR records are correct when the call is answered before the transfer
ocurs.
I only consider this major, because without a working workaround i can not
upgrade to 1.6 and will have to continue with 1.4 
====================================================================== 

---------------------------------------------------------------------- 
 (0111916) foxfire (reporter) - 2009-10-06 12:21
 https://issues.asterisk.org/view.php?id=16026#c111916 
---------------------------------------------------------------------- 
Thax that was quick.
I did some more tests, most fields are correct 
such as clid,src.dst,channel,dstchannel ,lastapp,lastdata
but userfield is wrong
i set the userfield with the call and billing option for example:

userfield=3001,003519232322,TRUNK1,ROUTE:003519

later on i can decide depending the case who to bill the call to
What is happening is that i get the wrong userfield i get the acct of the
internal call 

userfield=3003,3001

so the call will not get billed.
For now i found a very ugly workaround.
first i changed lastdata size to 256.
next i am dialing for example with
Dial(IAX2/log at pr/003519232322,60,RTtWwKk,,3001,003519232322,TRUNK1,ROUTE:003519)
because there are no 5 and 6 argument in dial it will not confict and the
string goes into the CDR.
As i said this is ugly an unprofessional i would love if this would work
the other way 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-06 12:21 foxfire        Note Added: 0111916                          
======================================================================