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

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jan 29 09:43:10 CST 2010


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:                     new
Asterisk Version:           SVN 
JIRA:                        
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-01-29 09:43 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0117368) haakon (reporter) - 2010-01-29 09:43
 https://issues.asterisk.org/view.php?id=16732#c117368 
---------------------------------------------------------------------- 
I forgot to add documentation for the manager commands.

Leif, is this good enough documentation? If so, I will add it, and upload
a new patch at once. Else, give me pointers :)

        <manager name="DeviceStateGet" language="en_US">
                <synopsis>
                        Get DeviceState information.
                </synopsis>
                <syntax>
                        <xi:include
xpointer="xpointer(/docs/manager[@name='Login']/syntax/parameter[@name='ActionID'])"
/>
                        <parameter name="DeviceName" required="true" />
                </syntax>
                <description>
                        <para>The DeviceStateGet command can be used to
get custom device states.</para>
                        <para>The result will be returned through a
DeviceStateGetResponse event.</para>
                </description>
        </manager>
        <manager name="DeviceStateSet" language="en_US">
                <synopsis>
                        Set DeviceState information.
                </synopsis>
                <syntax>
                        <xi:include
xpointer="xpointer(/docs/manager[@name='Login']/syntax/parameter[@name='ActionID'])"
/>
                        <parameter name="DeviceName" required="true" />
                        <parameter name="DeviceState" required="true" />
                </syntax>
                <description>
                        <para>The DeviceStateSet command can be used to
set custom device states.</para>
                        <para>The possible DeviceState values for this
function are:</para>
                        <para>UNKNOWN | NOT_INUSE | INUSE | BUSY | INVALID
| UNAVAILABLE | RINGING |
                        RINGINUSE | ONHOLD</para>
                </description>
        </manager> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-29 09:43 haakon         Note Added: 0117368                          
======================================================================




More information about the asterisk-bugs mailing list