[asterisk-bugs] [JIRA] (ASTERISK-21552) AMI 1.4 Improvements - Refactor AMI/CLI channel inspection actions to use the stasis channel cache

Matt Jordan (JIRA) noreply at issues.asterisk.org
Wed Apr 17 21:57:03 CDT 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-21552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21552:
-----------------------------------

    Status: Open  (was: Triage)
    
> AMI 1.4 Improvements - Refactor AMI/CLI channel inspection actions to use the stasis channel cache
> --------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21552
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21552
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Core/ManagerInterface, Core/Stasis
>            Reporter: Matt Jordan
>              Labels: Asterisk12
>
> In order to minimize locking and interference with channels, AMI should attempt to use the stasis cache where possible when looking up data on a channel. This includes the following:
> h4. manager.c
> * GetVar - channel snapshots should contain their channel variables. We can simply look at the snapshot's manager_vars field and return the value from it.
> * CoreShowChannels - this should only hit the Stasis channel cache.
> h4. cli.c
> * core show channels - inspect the channels using the stasis cache
> * core show channel. It may be worthwhile to not print out the information that can't be obtained from the cache, simply to minimize the impact of this command.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list