[asterisk-dev] [Code Review] 3903: Stasis: Allow internal channels directly into bridges

rmudgett reviewboard at asterisk.org
Mon Aug 11 13:41:47 CDT 2014


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



branches/12/res/res_stasis.c
<https://reviewboard.asterisk.org/r/3903/#comment23514>

    This variable is effectively unused.  Nothing seems to care about the value set in res.  That is unless you actually intend to return the value but forgot to.


- rmudgett


On Aug. 11, 2014, 1:35 p.m., opticron wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3903/
> -----------------------------------------------------------
> 
> (Updated Aug. 11, 2014, 1:35 p.m.)
> 
> 
> Review request for Asterisk Developers, Matt Jordan and Mark Michelson.
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> The patch to catch channels being shoehorned into Stasis() via external mechanisms also happens to catch Announcer and Recorder channels because they aren't known to be stasis-controlled channels in the usual sense. This marks those channels as Stasis()-internal channels and allows them directly into bridges.
> 
> 
> Diffs
> -----
> 
>   branches/12/res/stasis/stasis_bridge.c 420591 
>   branches/12/res/res_stasis.c 420591 
>   branches/12/res/ari/resource_bridges.c 420591 
>   branches/12/include/asterisk/stasis_app.h 420591 
> 
> Diff: https://reviewboard.asterisk.org/r/3903/diff/
> 
> 
> Testing
> -------
> 
> Ensured this patch fixed rest_api/bridges/playback/tones and rest_api/bridges/bridge_record tests.
> 
> 
> Thanks,
> 
> opticron
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140811/de6a6272/attachment.html>


More information about the asterisk-dev mailing list