Allowing buffering a LNTF (loss notification) feedback message in RTCPSender
Loss notifications may either be sent immediately, or wait until another RTCP feedback message is sent. Bug: webrtc:10336 Change-Id: I40601d9fa1dec6c17b2ce905cb0c8cd2dcff7893 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/139242 Commit-Queue: Elad Alon <eladalon@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28142}
This commit is contained in:
@ -181,7 +181,7 @@ void LossNotificationController::HandleLoss(uint16_t last_received_seq_num,
|
||||
last_decodable_non_discardable_->first_seq_num));
|
||||
loss_notification_sender_->SendLossNotification(
|
||||
last_decodable_non_discardable_->first_seq_num, last_received_seq_num,
|
||||
decodability_flag);
|
||||
decodability_flag, /*buffering_allowed=*/true);
|
||||
} else {
|
||||
key_frame_request_sender_->RequestKeyFrame();
|
||||
}
|
||||
|
Reference in New Issue
Block a user