On Mon, Dec 8, 2008 at 2:28 AM, Paul Whitfield <[EMAIL PROTECTED]> wrote: > Alexander Chemeris wrote: >> On Fri, Dec 5, 2008 at 4:06 AM, Paul Whitfield <[EMAIL PROTECTED]> wrote: >>> >>> What is the current status of RTCP support in sipxtapi? >> >> Sadly RTCP code in the current sipXtapi is broken in some places. >> I'm not sure about amounts of this breakage, but it's not that it just >> not hooked up. The code itself should be fixed. > > I have been "playing" around with the RTCP code that exists, > and have got it "working"... I.e. I have got it sending > Receiver Reports and Sender Reports. I have not checked that the > contents of the reports are correct.
IIRC, there were also a problem with memory leaks in RTCP code, which was fixed. >> Good news are >> we have a fixed and refactored version of the RTCP code, but we >> have it in a form of a patch against very old sipXtapi version. >> I'm pretty sure that RTCP code itself haven't changed since then, >> so you can simply replace currect code with what we have, >> but media processing code have changed. So this part should >> be reviewed and manually updated to recent version of sipXmediaLib. >> >> If you want to help us with the merge - I'll send you the patch. But >> you should commit to share results of your merge with the community. :) > > I would be happy to do the merge and provide the results back. Ok, I'll work on negotiating this. We should get an approval from the code owner to publish it. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
