hi,<br>Im taking a look at func_devstate.c and i see that I can only set Custom states.<br>Here's the problem:<br><br> -- Executing [5145554188@incomingUnlimitel:1] NoOp("IAX2/5145554188-10", "SIP/1004 has state NOT_INUSE") in new stack
<br> -- Executing [5145554188@incomingUnlimitel:2] Set("IAX2/5145554188-10", "DEVSTATE(SIP/1004)=BUSY") in new stack<br>[Jan 15 18:39:19] WARNING[17840]: func_devstate.c:120 devstate_write: The DEVSTATE function can only be used to set 'Custom:' device state!
<br> -- Executing [5145554188@incomingUnlimitel:3] NoOp("IAX2/5145554188-10", "SIP/1004 has now NOT_INUSE") in new stack<br><br><br>what about if you want to change current state (mainly from BUSY to NOT_INUSE)
<br><br>So I've take a look at:<br>func_devstate.c::devstate_write() to just comment the block checking for Custom, but i simply got:<br><br><br> -- Executing [5145554188@incomingUnlimitel:1] NoOp("IAX2/5145554188-1", "SIP/1004 has state NOT_INUSE") in new stack
<br> -- Executing [5145554188@incomingUnlimitel:2] Set("IAX2/5145554188-1", "DEVSTATE(SIP/1004)=BUSY") in new stack<br> -- Executing [5145554188@incomingUnlimitel:3] NoOp("IAX2/5145554188-1", "SIP/1004 has now NOT_INUSE") in new stack
<br><br>So it's like the devstate has not be successfully set and I'd like to know exactly.<br><br>I realized Custom devstate are written to astDB, and after it's calling __ast_device_state_changed_literal(), and there, its should change the state, no?
<br><br><br>After a quick discussion with Russell on IRC, he told me the answers is pretty long why we can explicitly change a device state.<br><br>So let's start a discussion around this :)<br><br clear="all"><br>--
<br>Clod Patry