Summary:	ASTERISK-16404: [branch] Pinefrog - RTCP improvements
Reporter:	Olle Johansson (oej)	Labels:
Date Opened:	2010-07-22 08:12:59	Date Closed:	2018-12-14 10:49:42.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/RTP
Versions:		Frequency of Occurrence
Related Issues:	is related to ASTERISK-15171 RTPAUDIOQOS and RTPAUDIOQOSBRIDGED false statistics is related to ASTERISK-18455 RTCP stats works only when transcoding is related to ASTERISK-20754 rtp_engine's RTCP{Sent,Received} events should contain the Channel name
Environment:		Attachments:
Description:	The pinefrog branch includes a lot of RTCP improvements for Asterisk. See the readme at http://svnview.digium.com/svn/asterisk/team/oej/pinefrog-1.4/README.pinefrog-rtcp for details. The code exists for 1.4 currently, but work is under way to port it to trunk. I would love seeing this in 1.8, but can not get it done to tomorrow.
Comments:	By: Russell Bryant (russell) 2010-07-22 13:16:18 Do you have a timeframe when you think the port will be done and ready for review? By: Olle Johansson (oej) 2010-07-23 01:46:11 I have a contractor that agreed to do it, but have no timestamp to set on it yet. Will try to finalize one and get back to you. By: Leif Madsen (lmadsen) 2010-09-09 12:25:02 Any movement here? By: Rafael Prado Rocchi (prado) 2010-10-08 13:35:49 Oej, we are testing a lot your deluxepine branch. What's the difference from this branch? By: Leif Madsen (lmadsen) 2011-02-08 13:44:08.000-0600 Marked as confirmed as there is a branch (code) but this needs to be ported to trunk in order to move this to Ready For Testing. By: Luke H (luckman212) 2012-01-25 08:50:12.638-0600 Did any of this work make it into the 1.8 branch?  The http://svnview.digium.com/svn/asterisk/team/oej/pinefrog-1.4/README.pinefrog-rtcp  link is dead now, is any further work being done related to RTCP? By: Olle Johansson (oej) 2012-01-25 13:58:07.489-0600 The link works fine for me. We have this code in production on a large amount of servers since almost a year. It really improves a lot of QoS issues. Currently, there's no funding for porting this to trunk and it's not part of 1.8. By: Luke H (luckman212) 2012-01-25 15:47:00.803-0600 Hmm, the link started working again! Sad to hear this never got ported to 1.8/10,  seems like really neat stuff. I'm curious how it affects QoS -- are you referring to better jitterbuffer adjustments based on the RTCP responses? How much funding is needed?  I think it's worth looking at, I would donate towards a bounty. By: Olle Johansson (oej) 2012-01-26 01:50:54.143-0600 Luke - contact me by e-mail oej@edvina.net It doesn't affect the actual QoS, bad wording from my side. It does improve the QoS reporting so you can manage your system better and so that the other end can take actions if needed (and if they can). We have a database with an entry for every call leg that we analyze and base routing on.