[asterisk-dev] distributed device state: xmpp and res_corosync

[Klaus Darilion]

Hi!

Nice to read that res_corosync replaces ais. So I read the documentation 
about res_corosync and unfortunately it lacks several real important 
information (also the xmmp solution). Thus, it would be great if someone 
can answer this questions by documenting the behavior in the respective 
wiki sections.

XMPP: What happens with state changes if the publishing Asterisk server 
is not connected to the XMPP server. Will Asterisk publish the last 
state on reconnection?

What happens with state changes if the receiving Asterisk server is not 
connected to the XMPP server. Will the XMPP server publish the last 
state on reconnection?

Corosync: Is the state distribution with corosync reliable or not? What 
if there is packet loss and a single packet is lost? Are there any means 
to detect the loss and re-transmit state changes?

Lifetime: IIRC res_ais did not published a lifetime for the events. 
Thus, e.g. if a device is "in a call" and the subsequent "idle" message 
is lost, the device stays "in a call" until the next state change (which 
may not come at all).

Does this problem still exists in res_corosynch? What about XMPP? Do 
XMPP-state events have a lifetime. I think it would be good to define 
event lifetimes, at least for "in a call, ringing ..." states.

IMO it would be very important to document the state distribution 
behavior in detail.

Thanks
Klaus