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
While RCE_SEND_ONLY and RCE_RECEIVE_ONLY work fine for RTP, the situation becomes more complicated when it comes to RTCP. When only sending, we should also have the local address and port so we can bind to it for receiving RTCP receiver reports. Similarly, the receiver does not know the sender address, so the remote address should be deduced from somewhere (check RFC 3550), probably sender reports so that receiver reports can be setn to the sender.
The text was updated successfully, but these errors were encountered:
jrsnen
changed the title
Figure out how RTCP should be handled with RCE_SEND_ONLY and RCE_RECEIVE_ONLY
RTCP with RCE_SEND_ONLY and RCE_RECEIVE_ONLY flags
Nov 14, 2024
While RCE_SEND_ONLY and RCE_RECEIVE_ONLY work fine for RTP, the situation becomes more complicated when it comes to RTCP. When only sending, we should also have the local address and port so we can bind to it for receiving RTCP receiver reports. Similarly, the receiver does not know the sender address, so the remote address should be deduced from somewhere (check RFC 3550), probably sender reports so that receiver reports can be setn to the sender.
The text was updated successfully, but these errors were encountered: