Summary:	ASTERISK-14686: [patch] Custom devices do not interoperate with distributed events properly
Reporter:	Bradley Watkins (marquis)	Labels:
Date Opened:	2009-08-20 14:29:35	Date Closed:	2011-06-07 14:07:47
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Functions/func_devstate
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) func_devstate_with_distributed_events.patch
Description:	Since func_devstate isn't subscribing to events, it has no way of knowing when the state changes on a remote node and thus can't (and doesn't) update the AstDB accordingly.
Comments:	By: Russell Bryant (russell) 2009-09-11 07:11:42 AstDB should not have the full distributed device state stored away.  It should only have the per-server state stored there.  When something subscribes to a Custom state, they are not getting a value straight from here.  There is code in devicestate.c that takes the known states for all nodes and determines what the overall state value is. What problem did you encounter that led you to making this change? By: Bradley Watkins (marquis) 2009-09-14 13:13:07 OK, this turned out to be a misunderstanding on my part.  I based my opinion on the output of a 'devstate list' rather than doing something that would actually look at what Asterisk thought the state was for a give Custom device. By: Leif Madsen (lmadsen) 2009-09-14 14:12:52 Closed per the reporter. Thanks!