diff options
| author | Jeff Peeler <jpeeler@digium.com> | 2009-10-17 01:36:08 +0000 |
|---|---|---|
| committer | Jeff Peeler <jpeeler@digium.com> | 2009-10-17 01:36:08 +0000 |
| commit | 53a95d9c8483c3cd7b5ead9a459bce6e62bd5331 (patch) | |
| tree | df9888cbbe0fd60405fd5e91d423901844b34fb0 /main | |
| parent | 64a32b3ad055869ed3d59da8ec813c4db5d6371f (diff) | |
Merged revisions 224330 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r224330 | jpeeler | 2009-10-16 20:32:47 -0500 (Fri, 16 Oct 2009) | 13 lines
Fix stale caller id data from being reported in AMI NewChannel event
The problem here is that chan_dahdi is designed in such a way to set
certain values in the dahdi_pvt only once. One of those such values
is the configured caller id data in chan_dahdi.conf. For PRI, the
configured caller id data could be overwritten during a call. Instead
of saving the data and restoring, it was decided that for all non-analog
channels it was simply best to not set the configured caller id in the
first place and also clear it at the end of the call.
(closes issue #15883)
Reported by: jsmith
........
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@224331 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'main')
0 files changed, 0 insertions, 0 deletions