[asterisk-bugs] [Asterisk 0016468]: Custom devsate set to INUSE but shows as UNAVAILABLE when accessing through the dialplan

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16468 
====================================================================== 
Reported By:                millsu2
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16468
Category:                   Functions/func_devstate
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.11 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-18 16:02 CST
Last Modified:              2009-12-18 17:00 CST
====================================================================== 
Summary:                    Custom devsate set to INUSE but shows as UNAVAILABLE
when accessing through the dialplan
Description: 
I set a custom device state to "INUSE" using
Set(DEVICE_STATE(Custom:device)=INUSE). Through "database show" or 
"devstate list" the state is listed as "INUSE" as it should, but when
getting the state in the dialplan using ${DEVICE_STATE(Custom:device)} it
returns "UNAVAILABLE". If I do "devstate change Custom:device INUSE" after
this happens then it works properly.
====================================================================== 

---------------------------------------------------------------------- 
 (0115442) millsu2 (reporter) - 2009-12-18 17:00
 https://issues.asterisk.org/view.php?id=16468#c115442 
---------------------------------------------------------------------- 
This issue did not exist in 1.6.1.1. It showed up after upgrading to
1.6.1.11 and no changes were made to the dialplan. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-18 17:00 millsu2        Note Added: 0115442                          
======================================================================