summaryrefslogtreecommitdiff
path: root/include/asterisk/event_defs.h
diff options
context:
space:
mode:
authorDavid Vossel <dvossel@digium.com>2010-08-13 18:58:49 +0000
committerDavid Vossel <dvossel@digium.com>2010-08-13 18:58:49 +0000
commit86142d711f40bb582e0bfea311ec10b93ef7d60a (patch)
tree5ccd2dac6a20bfd5d9d63e70011e4bba7b5a83d3 /include/asterisk/event_defs.h
parent75033d0735c9ac52d667de1377bf8c7083ce788c (diff)
Merged revisions 282236 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8 ................ r282236 | dvossel | 2010-08-13 13:58:10 -0500 (Fri, 13 Aug 2010) | 23 lines Merged revisions 282235 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.6.2 ........ r282235 | dvossel | 2010-08-13 13:54:53 -0500 (Fri, 13 Aug 2010) | 16 lines only do magic pickup when notifycid is enabled A new way of doing BLF pickup was introduced into 1.6.2. This feature adds a call-id value into the XML of a SIP_NOTIFY message sent to alert a subscriber that a device is ringing. This option should only be enabled when the new 'notifycid' option is set... but this was not the case. Instead the call-id value was included for every RINGING Notify message, which caused a regression for people who used other methods for call pickup. (closes issue #17633) Reported by: urosh Patches: chan_sip.txt uploaded by urosh (license ) blf_cid_issue.diff uploaded by dvossel (license 671) Tested by: dvossel, urosh, okrief, alecdavis ........ ................ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@282237 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'include/asterisk/event_defs.h')
0 files changed, 0 insertions, 0 deletions