You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RTCP framework should send RTCP RR when it's not transmitting anything.
Currently the transmission of RTCP was driven by transmission of RTP, so when an endpoint is only actively listening (and not sending anything, although stream direction is send-recv), then no RTCP packet is sent.
2007-09-20 12:32:59: @bennylpchanged status from new to closed
2007-09-20 12:32:59: @bennylpset resolution to fixed
The pjmedia_rtcp_build_rtcp() function now may create RTCP SR (Sender Report) or RR (Receiver Report) depending on whether the endpoint has been transmitting RTP packets since the last interval.
2007-09-20 12:29:36: @bennylp created the issue on trac ticket 377
This is duplicate of ticket #13 for trunk.
The RTCP framework should send RTCP RR when it's not transmitting anything.
Currently the transmission of RTCP was driven by transmission of RTP, so when an endpoint is only actively listening (and not sending anything, although stream direction is send-recv), then no RTCP packet is sent.
2007-09-20 12:32:59: @bennylp changed status from new to closed
2007-09-20 12:32:59: @bennylp set resolution to fixed
2007-09-20 12:32:59: @bennylp commented
Implemented in r1444.
The
pjmedia_rtcp_build_rtcp()
function now may create RTCP SR (Sender Report) or RR (Receiver Report) depending on whether the endpoint has been transmitting RTP packets since the last interval.2007-09-20 13:09:51: @bennylp commented
In r1445:
Fixed bug in RTCP fraction_lost calculation: the first RTCP packet always shows positive fraction loss
2007-09-20 13:41:04: @bennylp commented
In r1446: Fixed bug in incoming RTCP RR handling because the RTCP packet structure has been changed in r1444
The text was updated successfully, but these errors were encountered: