[asterisk-dev] [Code Review]: chan_ooh323 direct rtp (remote bridging) support

[may213]

> On Dec. 6, 2011, 10:17 a.m., Paul Belanger wrote:
> > Might be worth doing :retab on these files, lots of red blogs; too many to point out.  Also, I see a lot of CODING-GUIDELINE issues:  EG if statements should be:
> > 
> > if (bar()) {
> >      blah();
> > } else {
> >      foo();
> > }
> > 
> > It would be good to review the document.
> >

pointed issues fixed in r2 patch for changed codes. Most of pointed issues are in the codes that already commited previously and not changed for this review. I think that reformat all codes and post diff for these here isn't good idea and this must be done as separate work.


- may213


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


On Dec. 9, 2011, 1:03 p.m., may213 wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/1607/
> -----------------------------------------------------------
> 
> (Updated Dec. 9, 2011, 1:03 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> There is direct rtp support for chan_ooh323 channel driver.
> It work like chan_sip direct rtp support based on directmedia (directrtp) option that can be global or per peer/user.
> Also there is earlydirect (directrtpsetup) option that allow setup direct rtp connection for early media.
> 
> On h.323 side there can be two modes to enable direct rtp - with or without renegotiation media channels.
> If there are opened media channels (logical channels in h.323) then renegotiation must be done and it caused by
> sending empty terminalcapabilities set to opposite side.  If empty tcs is arrived transmit logical channels
> will be closed then reopen with new rtp addresses.
> if there are no opened channels then new rtp addresses come in the new fast start proposal or just saved 
> for further use in the channel open negotiation (it is for fast start disabled case).
> 
> 
> Diffs
> -----
> 
>   /trunk/addons/Makefile 347865 
>   /trunk/addons/chan_ooh323.h 347865 
>   /trunk/addons/chan_ooh323.c 347865 
>   /trunk/addons/ooh323c/src/ooCalls.h 347865 
>   /trunk/addons/ooh323c/src/ooCmdChannel.c 347865 
>   /trunk/addons/ooh323c/src/ooLogChan.h 347865 
>   /trunk/addons/ooh323c/src/ooLogChan.c 347865 
>   /trunk/addons/ooh323c/src/ooStackCmds.h 347865 
>   /trunk/addons/ooh323c/src/ooStackCmds.c 347865 
>   /trunk/addons/ooh323c/src/ooh245.h 347865 
>   /trunk/addons/ooh323c/src/ooh245.c 347865 
>   /trunk/addons/ooh323c/src/ooh323.c 347865 
>   /trunk/addons/ooh323c/src/ooh323ep.c 347865 
>   /trunk/addons/ooh323c/src/ooq931.h 347865 
>   /trunk/addons/ooh323c/src/ooq931.c 347865 
>   /trunk/addons/ooh323cDriver.c 347865 
> 
> Diff: https://reviewboard.asterisk.org/r/1607/diff
> 
> 
> Testing
> -------
> 
> h.323->h.323 (fast start enabled & disabled), h.323->sip, sip->h.323 remote bridging are tested and work well.
> Another rtp based channels (sccp, jingle) are not tested but must work.
> 
> 
> Thanks,
> 
> may213
> 
>

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