diff options
author | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-10-17 01:58:45 +0000 |
---|---|---|
committer | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-10-17 01:58:45 +0000 |
commit | 6c04bfb36f789e5ae784027d1a42a6b085aea0f3 (patch) | |
tree | 5b3a4229e68f208ad706ba44acc1390e7ba50b4a /configs | |
parent | 224a1a328854f27bb54071d3ef06e47215ed580b (diff) |
Merged revisions 224331 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
................
r224331 | jpeeler | 2009-10-16 20:36:08 -0500 (Fri, 16 Oct 2009) | 20 lines
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: http://svn.digium.com/svn/asterisk/branches/1.6.2@224334 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs')
0 files changed, 0 insertions, 0 deletions