[asterisk-bugs] [Asterisk 0011774]: CALLERID is not logged correctly into cdrs

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11774 
====================================================================== 
Reported By:                voipgate
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11774
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-15-2008 14:53 CST
Last Modified:              01-22-2008 10:00 CST
====================================================================== 
Summary:                    CALLERID is not logged correctly into cdrs
Description: 
I can set my callerid using the CALLERID function and this works great on
the dialplan. I can read and write to it,the callerid is applied, but
inside the cdr records it is the first callerid that has been provided and
not the one that i defined.


If I modify my CALLERID it should be logged to the cdr table.
====================================================================== 

---------------------------------------------------------------------- 
 licedey - 01-22-08 10:00  
---------------------------------------------------------------------- 
Corydon76: in the cdr.conf I didn't have "endbeforehexten" option set.
Isn't it set to "no" by default? I will try to add endbeforehexten=no to
cdr.conf, but I think it will not work, since I tried to modify the
callerid before h or even before the dial application was executed. 

I use a work around to correct the caller id. instead of changing
cdr(clid) in the dial plan I modify the cdr(userfield),which I don't use,
the cdr is stored into the cdr_pgsql. I added a trigger to my postgres
database, when userfield has value, it corrects the clid and src fields. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-22-08 10:00  licedey        Note Added: 0081025                          
======================================================================