On 19 Mar 2014, at 15:41, Matthew Jordan <[email protected]> wrote:
> On Wed, Mar 19, 2014 at 9:26 AM, Olle E. Johansson <[email protected]> wrote: > > <snip> > >> While working on Pinana we realized that th XMPP stuff was not >> handling device/extension states correctly - I worked with the >> developer of the XMPP state distribution in my design and we >> realized that he had missed the distinction. >> >> We need to be able to publish device states for aggregation into >> extension states, but also publish extension states for blinking >> lamps. IE, a hint would be based on a device state subscription. >> > > Fundamentally, I've been thinking about this problem more around > device states: that is, if all Asterisk instances have the ability to > share their device states - whatever those device states happen to > derive from - then every Asterisk instance can build the same > extension states if they so choose to. Or not - but it ends up being a > function of the Asterisk dialplan at each instance, as opposed to > something forced. > > In a world where all Asterisk instances know of the device states for > any other Asterisk instance, can you explain why publishing extension > states are needed? As I said - to off load NOTIFications to phones for blinking lamps. Asterisk PUBLISH extension state to the proxy. The proxy manages all the subscriptions. Everyone is happy and do what they do best. /O -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
