[asterisk-bugs] [Asterisk 0015613]: Changes to CALLERID don't get propagated to CDR(clid)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15613 
====================================================================== 
Reported By:                pyves
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15613
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-30 02:08 CDT
Last Modified:              2009-07-31 01:13 CDT
====================================================================== 
Summary:                    Changes to CALLERID don't get propagated to
CDR(clid)
Description: 
Whenever I make changes to CALLERID, using Set(CALLERID(num)=....) or
PrivacyManager() in the dialplan, the changes don't propagate to CDR(clid).
Whatever caller id was sent over by the SIP client (and I've tried many SIP
clients, soft and hard, to ensure there wasn't a client issue) sticks to
CDR(clid) and hence my cdr backends (and this occurs with both csv and
sqlite3) aren't reflecting the correct clid. This is obviously particularly
problematic while using PrivacyManager(), as you loose the information
being provided by the caller.

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

---------------------------------------------------------------------- 
 (0108446) pyves (reporter) - 2009-07-31 01:13
 https://issues.asterisk.org/view.php?id=15613#c108446 
---------------------------------------------------------------------- 
First of all, I forgot to mention this occurs with IAX2 as well, and if I'm
not mistaken there isn't any caller presentation set of options with IAX2.
In any case, I've checked my SIP caller presentation setting, and it's at
the default of "allowed_not_screened". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-31 01:13 pyves          Note Added: 0108446                          
======================================================================