[asterisk-dev] [Code Review] 2645: Use stasis cache in more places

[opticron]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/2645/#review8977
-----------------------------------------------------------



/trunk/main/cli.c
<https://reviewboard.asterisk.org/r/2645/#comment17658>

    Blob.



/trunk/main/cli.c
<https://reviewboard.asterisk.org/r/2645/#comment17659>

    Blob.



/trunk/main/manager.c
<https://reviewboard.asterisk.org/r/2645/#comment17660>

    This seems very similar to BridgeList and BridgeInfo in manager_bridging.c



/trunk/main/manager.c
<https://reviewboard.asterisk.org/r/2645/#comment17661>

    You should use ast_manager_build_channel_state_string() to build the standard channel AMI blob from the snapshot and avoid code duplication.



/trunk/main/manager.c
<https://reviewboard.asterisk.org/r/2645/#comment17662>

    You should use ast_manager_build_bridge_state_string for items that it covers even though it's currently pretty minimal.



/trunk/main/manager.c
<https://reviewboard.asterisk.org/r/2645/#comment17663>

    Idem.


- opticron


On June 26, 2013, 7:58 a.m., Joshua Colp wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2645/
> -----------------------------------------------------------
> 
> (Updated June 26, 2013, 7:58 a.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Bugs: ASTERISK-21883
>     https://issues.asterisk.org/jira/browse/ASTERISK-21883
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> This change moves CLI/AGI/AMI commands to accessing the Stasis cache for retrieving information instead of directly accessing the data structures. I have also added an AMI action to get bridge information, and extended the "status" action to include the same information available as "core show channel".
> 
> Stuff given up:
> 1. Number of frames being read and written
> 2. First file descriptor
> 3. What the channel is blocked in
> 
> An additional question:
> I'm not currently storing channel trace information in the snapshot and as a result it is not displayed. Is this a feature we still want to support? How widespread is it?
> 
> 
> Diffs
> -----
> 
>   /trunk/include/asterisk/channel.h 392949 
>   /trunk/include/asterisk/stasis_channels.h 392949 
>   /trunk/main/bridging.c 392949 
>   /trunk/main/channel.c 392949 
>   /trunk/main/channel_internal_api.c 392949 
>   /trunk/main/cli.c 392949 
>   /trunk/main/manager.c 392949 
>   /trunk/main/pbx.c 392949 
>   /trunk/main/stasis_channels.c 392949 
>   /trunk/res/res_agi.c 392949 
> 
> Diff: https://reviewboard.asterisk.org/r/2645/diff/
> 
> 
> Testing
> -------
> 
> Executed the changed CLI commands, AMI actions, and AGI commands and ensured that the output is as expected.
> 
> 
> Thanks,
> 
> Joshua Colp
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130626/cb4b84df/attachment-0001.htm>