diff options
| author | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-01-12 00:20:55 +0000 |
|---|---|---|
| committer | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-01-12 00:20:55 +0000 |
| commit | cdf9ce4cb99c864703ce33a58563f3c65ef15daf (patch) | |
| tree | 38a0f71dccacbaa7c51b2ce32a80611d99dec9a8 /CHANGES | |
| parent | 7b0ce5ebecbce6ef25862a092eaee89a62189773 (diff) | |
Add 'zap set dnd' CLI command, and ensure that the AMI DNDState event always gets generated.
(closes issue #11212)
Reported by: tzafrir
Patches:
zap_dnd.diff uploaded by tzafrir (modified by me) (license 46)
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@98488 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -197,6 +197,9 @@ Zaptel channel driver (chan_zap) Changes does not specify signalling for a channel (which is unlikely as the sample configuration file has always recommended specifying it for every channel) then the 'auto' mode will be used for that channel if possible. + * Added a 'zap set dnd' command to allow CLI control of the Do-Not-Disturb + state for a channel; also ensured that the DNDState Manager event is + emitted no matter how the DND state is set or cleared. A new channel driver: Unistim ----------------------------- |