<br><br><div class="gmail_quote">On Mon, Nov 8, 2010 at 12:48 PM, Russell Bryant <span dir="ltr"><<a href="mailto:russell@digium.com">russell@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
<br>
</div>In the case of res_ais, it works by having every server report state<br>
changes that occur on that server. The result is that each server has<br>
an internal table of the state of each device from the perspective on<br>
each server involved. When the state changes on _any_ server, it then<br>
looks at the last known state of that device on all servers and<br>
determines an overall state. So, based on that, this is supposed to<br>
work.<br>
<br>
The way this works is that each event is tagged with a server ID<br>
(referred to as an entity ID, or EID). From a quick look at the XMPP<br>
implementation, it appears that the server ID is not being propagated.<br>
So, the failure you are seeing is not ideal (a bug actually, please<br>
report it), but it is the expected behavior right now.<br>
<br>
The XMPP distributed device state code needs to be updated such that the<br>
EID information element is included in state changes that it sends out<br>
such that its behavior matches that of the AIS implementation.<br></blockquote></div><br>Clearly this was a misunderstanding on my part about how the EID is being used in AIS. My impression was that it was primarily being used to prevent event feedback loops.<br>
<br>At any rate, if you would please open a bug Klaus and have someone assign it to me I'll make sure this gets fixed in the next week or so.<br><br>- Brad<br>