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

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16468 
====================================================================== 
Reported By:                millsu2
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   16468
Category:                   Functions/func_devstate
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     closed
Target Version:             1.6.1.15
Asterisk Version:           SVN 
JIRA:                       SWP-582 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-12-18 16:02 CST
Last Modified:              2010-02-05 10:02 CST
====================================================================== 
Summary:                    [patch] [regression] 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.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0016140 hint not updated correctly on outgoing ...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-05 10:02 dvossel        Resolution               open => no change
required
======================================================================