[asterisk-bugs] [Asterisk 0014590]: updatecdr='yes' in agents.conf is not working

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14590 
====================================================================== 
Reported By:                msetim
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14590
Category:                   Channels/chan_agent
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-02 19:51 CST
Last Modified:              2009-08-03 10:41 CDT
====================================================================== 
Summary:                    updatecdr='yes' in agents.conf is not working
Description: 
Hi guys,

I have been update my asterisk from 1.4.20.1 to 1.4.23.1 (last release)
and updatecdr='yes' doesn't work anymore. I don't change anything in
configuration and it don't work. When I made downgrade to 1.4.20.1 the
updatecdr back to work again.

Well, I really don't know what to post here to help because I only change
the asterisk. My configuration is:

agents.conf

 autologoff=15
 ackcall=yes
 updatecdr=yes
 savecallsin=/var/spool/asterisk/agent
 endcall=yes
 wrapuptime=5000
 createlink=no
 musiconhold=Silence
 recordagentcalls=yes

cdr_odbc.conf

[global]
dsn=PostgreSQL-asterisk
username=XXXXXXXX
password=XXXXXXXX
loguniqueid=yes
dispositionstring=yes
table=tb_cdr

PS. I try to set "I did not set the category correctly" but it give and
error saying that I need to set someone.

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

---------------------------------------------------------------------- 
 (0108543) Laureano (reporter) - 2009-08-03 10:41
 https://issues.asterisk.org/view.php?id=14590#c108543 
---------------------------------------------------------------------- 
After doing some research, I've tracked down this issue to the revision
127663. This revision includes a series of bug fixes that solves some
issues with CDRs.
Apparently, a change in res_features.c has modified the behavior of the
CDR engine when a call is bridged. In such case, and unless one of the CDRs
got zapped (pun unintentional), the userfield value from the B leg doesn't
get copied to the A leg.
The original behavior used to append the B leg's userfield to the A leg,
using a semicolon as field separator. But the new funcionality introduced
in the named revision seems to forgot about this appending, unless a
particular xfer takes place.

I've attached a patch which I'm using in one of my production systems
after upgrading to 1.4.25.1. The patch is only for illustrative purposes
and it's not intented to be considered as a patch to be included in trunk. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-03 10:41 Laureano       Note Added: 0108543                          
======================================================================