[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 13:21 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0117472) haakon (reporter) - 2010-02-01 13:21
 https://issues.asterisk.org/view.php?id=16732#c117472 
---------------------------------------------------------------------- 
What about adding a new class:
; devicestate - General information about devices. Read-only.

Where we later would also add other data that may be coming from channel
drivers about a specific device, not affiliated with calls, like these.

Maybe find another class name that doesn't sound so much like the device
states. deviceinfo, or as simple as deviceevents.

What do you think? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-01 13:21 haakon         Note Added: 0117472                          
======================================================================