[asterisk-dev] distributed device-state implementation question

Klaus Darilion klaus.mailinglists at pernau.at
Thu Jan 13 13:25:20 CST 2011

Russell Bryant wrote:
> On Thu, 2011-01-13 at 11:45 -0600, Russell Bryant wrote:
>> On Thu, 2011-01-13 at 16:47 +0100, Klaus Darilion wrote:
>> Excellent question.  The device state cache (which is independent of the
>> state distribution method) will remember the last known state of a
>> device on a given server.  If that server never comes back up, the state
>> on that server will be stuck at busy, which would mess things up.
> Actually, I don't think this applies to the SIP method being developed,
> since the state collection isn't done inside of Asterisk.  These
> comments only apply to the XMPP and AIS methods.

True, SIP based distribution with PUBLISH always have an expiry. On the 
other hand this requires Asterisk to republish states before they expire 
(pretty easy - just send a PUBLISH without body).


More information about the asterisk-dev mailing list