[asterisk-bugs] [Asterisk 0015613]: Changes to CALLERID don't get propagated to CDR(clid)
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jul 30 02:08:35 CDT 2009
The following issue has been SUBMITTED.
======================================================================
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-30 02:08 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-07-30 02:08 pyves New Issue
2009-07-30 02:08 pyves Asterisk Version => 1.6.1.0
2009-07-30 02:08 pyves Regression => No
2009-07-30 02:08 pyves SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list