[asterisk-bugs] [JIRA] (ASTERISK-20880) Add channel caching to event subsystem

[Kinsey Moore (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201376#comment-201376 ] 

Kinsey Moore commented on ASTERISK-20880:
-----------------------------------------

The bare minimum information required for the Newstate event:
Channel Name
Unique ID
Channel State
Caller ID
Connected Line Info

Other information that is likely to change:
Language
Music Class
Account Code
Parking Lot
User Field
AMA Flags
Hangup Source
Tone Zone
Named Call Group
Named Pickup Group
Bridged Channel Name
Context
Extension
Priority
Call Forward
Linked ID
Redirecting Info

The majority of this information must be represented as strings, but some like AMA Flags, Channel State, and Priority are integers.
                
> Add channel caching to event subsystem
> --------------------------------------
>
>                 Key: ASTERISK-20880
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20880
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Core/Stasis
>            Reporter: Matt Jordan
>              Labels: Asterisk12
>
> Elements built on top of Stasis-Core will need to subscribe for changes in the channel state and be able to query for a channel's current state. While Stasis-Core may eventually be a separate module/subsystem, for now it makes sense to build the functionality on top of the existing event pub/sub system.
> There are a couple of 'requirements' that a solution should meet:
> # {{ast_channel}} objects should not be passed directly. Events being raised should not affect the lifetime of the channel object and should not provide direct access to the {{ast_channel}} object, but should instead pass a copy of the necessary information. This helps keep event consumers thread-safe.
> # The channel information passed by the event subsystem does not have to be all information contained in a channel, but should carry the name, unique ID, state, and other information likely to change on a channel.
> # Alternatively, a key/value pair mechanism containing the updated parameters of the channel can be passed (using either {{ast_variable}} or typed tuples, as prototyped on https://reviewboard.asterisk.org/r/2248/
> As an initial candidate of consuming this information, AMI should be refactored to subscribe for channel state updates and send the event based on this information. The existing {{Newstate}} event should be refactored into manager.c and built on top of this information.

--
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