[asterisk-bugs] [Asterisk 0016468]: [patch] [regression] Custom devsate set to INUSE but shows as UNAVAILABLE when accessing through the dialplan
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 27 14:11:19 CST 2010
A NOTE has been added to this issue.
======================================================================
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: feedback
Target Version: 1.6.1.14
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:
======================================================================
Date Submitted: 2009-12-18 16:02 CST
Last Modified: 2010-01-27 14:11 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 ...
======================================================================
----------------------------------------------------------------------
(0117262) dvossel (administrator) - 2010-01-27 14:11
https://issues.asterisk.org/view.php?id=16468#c117262
----------------------------------------------------------------------
I've been made aware of another change that could possibly have resolved
this as well that is not yet in a release. The patch for it was posted to
this issue. https://issues.asterisk.org/view.php?id=16607
If you are able to, it may be worth trying the latest rev in svn to see if
this problem still exists.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-27 14:11 dvossel Note Added: 0117262
======================================================================
More information about the asterisk-bugs
mailing list