[asterisk-dev] [Code Review] 2840: Restore usefulness of the CEL Peer field

[Matt Jordan]

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



/branches/12/main/cel.c
<https://reviewboard.asterisk.org/r/2840/#comment18988>

    If you fail to get a single peer snapshot, you shouldn't bail. Just continue on in the loop and add what peer names you can extract.



/branches/12/tests/test_cel.c
<https://reviewboard.asterisk.org/r/2840/#comment18989>

    Same finding here.


- Matt Jordan


On Sept. 10, 2013, 3:40 p.m., opticron wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2840/
> -----------------------------------------------------------
> 
> (Updated Sept. 10, 2013, 3:40 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Bugs: ASTERISK-22393
>     https://issues.asterisk.org/jira/browse/ASTERISK-22393
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> This change makes the CEL peer field useful again for BRIDGE_ENTER and BRIDGE_EXIT events and fills the field with a comma-separated list of all channels in the bridge other than the channel that is entering or exiting.
> 
> 
> Diffs
> -----
> 
>   /branches/12/tests/test_cel.c 398744 
>   /branches/12/main/cel.c 398744 
>   /branches/12/include/asterisk/cel.h 398744 
> 
> Diff: https://reviewboard.asterisk.org/r/2840/diff/
> 
> 
> Testing
> -------
> 
> The CEL unit tests pass once they were modified to take peer field matching into account.
> 
> 
> Thanks,
> 
> opticron
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130925/5d763b67/attachment-0001.html>