[asterisk-dev] [Code Review] 2459: bridge_construction: apply Jitterbuffers at bridge join via the JITTERBUFFER function.

[Joshua Colp]

> On April 18, 2013, 11:04 a.m., Joshua Colp wrote:
> > /team/group/bridge_construction/bridges/bridge_simple.c, lines 58-59
> > <https://reviewboard.asterisk.org/r/2459/diff/1/?file=36159#file36159line58>
> >
> >     Since this is now a required implementation aspect of any bridge technology I'd prefer it to be documented in the bridging technology header file. Alternatively making it so it was part of bridging core would be nicer...
> 
> Matt Jordan wrote:
>     Do we want it applied on every bridge?
>     
>     I suppose it isn't necessarily harmful, but it probably isn't needed for the infinite wait bridge.

My slight fear is that further down the line we continue to create more technologies and it gets left out. It also makes it one less thing another implementor has to worry about. I'm fine if the decision is to ultimately keep it within the technology.


- Joshua


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


On April 17, 2013, 11:01 p.m., jrose wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/2459/
> -----------------------------------------------------------
> 
> (Updated April 17, 2013, 11:01 p.m.)
> 
> 
> Review request for Asterisk Developers, Matt Jordan and rmudgett.
> 
> 
> Bugs: ASTERISK-21333
>     https://issues.asterisk.org/jira/browse/ASTERISK-21333
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> This patch adds support for applying jitterbuffers based on channel settings for jitterbuffers when bridging channels with simple bridges and softmixed bridges by use of func_jitterbuffer.
> 
> 
> Diffs
> -----
> 
>   /team/group/bridge_construction/funcs/func_jitterbuffer.c 385983 
>   /team/group/bridge_construction/configs/confbridge.conf.sample 385983 
>   /team/group/bridge_construction/bridges/bridge_softmix.c 385983 
>   /team/group/bridge_construction/bridges/bridge_simple.c 385983 
>   /team/group/bridge_construction/CHANGES 385983 
>   /team/group/bridge_construction/include/asterisk/abstract_jb.h 385983 
>   /team/group/bridge_construction/main/abstract_jb.c 385983 
> 
> Diff: https://reviewboard.asterisk.org/r/2459/diff/
> 
> 
> Testing
> -------
> 
> Tested simple two way calls with SIP with the SIP option jbenable on and off.  While on the jitterbuffer is applied as expected and while off it is not applied. Note that this is different from behavior in trunk. In trunk if a SIP channel calls another SIP channel with jbenabled=yes, there generally will not be a jitterbuffer created unless jbforced is set. This is because trunk checks both channels in a two way bridge for the following condition:
> 
> if (((!c0_wants_jitter && c1_creates_jitter) || (c0_force_jb && c1_creates_jitter)) && c0_jb_enabled) {
>    /* jitter buffer creation flag is raised for c0 */
>    ...
> }
> 
> and since SIP has the wants_jitter flag enabled, the jitter buffer is not applied.
> 
> We are no longer reaching across the bridge to look at both channels when doing this, so the jitter buffer will be applied unconditionally on bridging. This means the jbforced option is no longer respected.
> 
> 
> Thanks,
> 
> jrose
> 
>

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