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

[svnbot]

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

(Updated April 25, 2013, 2:29 p.m.)


Status
------

This change has been marked as submitted.


Review request for Asterisk Developers, Matt Jordan and rmudgett.


Changes
-------

Committed in revision 386561


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/CHANGES 386018 
  /team/group/bridge_construction/funcs/func_jitterbuffer.c 386018 
  /team/group/bridge_construction/include/asterisk/abstract_jb.h 386018 
  /team/group/bridge_construction/main/abstract_jb.c 386018 
  /team/group/bridge_construction/main/bridging.c 386018 

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/20130425/ea3e238f/attachment.htm>