[asterisk-bugs] [JIRA] (ASTERISK-21105) Stasis Core - Refactor Device State support

[Matt Jordan (JIRA)]

Matt Jordan created ASTERISK-21105:
--------------------------------------

             Summary: Stasis Core - Refactor Device State support
                 Key: ASTERISK-21105
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21105
             Project: Asterisk
          Issue Type: Improvement
      Security Level: None
          Components: Core/Stasis
            Reporter: Matt Jordan
      Target Release: 12


Once the Stasis Core API is finished, we need to begin refactoring current consumers/producers on the event subsystem to take advantage of it. This includes Device State.

Publishers:
* {{res_jabber}}
* {{res_xmpp}}
* {{devicestate}}

Consumers:
* {{app_queue}}
* {{pbx}}
* {{ccss}}
* {{devicestate}}
* {{res_jabber}}
* {{res_xmpp}}

An important distinction that has to be worked out is {{res_xmpp}} and {{res_jabber}}'s knowledge of what is a local device on this system and what is a remote device state update. For remote device states that come in from an XMPP message, the device state has to be raised in the system. However, notifications that originated locally have to be raised externally, but not again in the system. Currently, this appears to be handled by having two different event types for device state ({{AST_EVENT_DEVICE_STATE}} and {{AST_EVENT_DEVICE_STATE_CHANGE}}); ideally, this would be unified and {{res_xmpp}}/{{res_jabber}} would know whether or not the device was local or external.

For now, assume that {{res_corosync}} will be disabled until we figure out how to re-transmit the currently supported items across the wire.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira