[asterisk-bugs] [Asterisk 0016732]: [patch] Add AMI support for device states

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16732 
====================================================================== 
Reported By:                haakon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16732
Category:                   Functions/func_devstate
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                       SWP-826 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 244040 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-29 09:28 CST
Last Modified:              2010-02-01 01:45 CST
====================================================================== 
Summary:                    [patch] Add AMI support for device states
Description: 
main/devicestate.c says Asterisk Manager Interface (AMI) gets DeviceState
events, but this is not true.

This patch adds a "DeviceStateChanged" event to AMI. And also introduces
AMI commands DeviceStateSet and DeviceStateGet to controll device states
from AMI, if func_devicestate is compiled in.
====================================================================== 

---------------------------------------------------------------------- 
 (0117417) oej (manager) - 2010-02-01 01:45
 https://issues.asterisk.org/view.php?id=16732#c117417 
---------------------------------------------------------------------- 
Read Leif's comment about Russell's comment again, so yes, if you want that
level of details Device state notifications make sense, but I still think
it has to be configurable. For a large installation, it will generate quite
a lot of events. If we move it to a specific category, people can turn it
on/off in manager.conf. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-01 01:45 oej            Note Added: 0117417                          
======================================================================