[rtp_rtcp] Fix potentional time difference between rtp and rtcp packets.

SetRtpState function was updating only rtp_sender start timestamp.
Now it updates both rtp_sender and rtcp_sender start timestamps.

BUG=webrtc:5433
R=stefan@webrtc.org

Review URL: https://codereview.webrtc.org/1628323003 .

Cr-Commit-Position: refs/heads/master@{#11393}
This commit is contained in:
Danil Chapovalov 2016-01-27 12:54:37 +01:00
parent b11e97a552
commit d673b0fa5d
2 changed files with 1 additions and 1 deletions

View File

@ -291,6 +291,7 @@ void ModuleRtpRtcpImpl::SetSequenceNumber(const uint16_t seq_num) {
bool ModuleRtpRtcpImpl::SetRtpStateForSsrc(uint32_t ssrc,
const RtpState& rtp_state) {
if (rtp_sender_.SSRC() == ssrc) {
SetStartTimestamp(rtp_state.start_timestamp);
rtp_sender_.SetRtpState(rtp_state);
return true;
}

View File

@ -1872,7 +1872,6 @@ uint32_t RTPSender::BitrateSent() const {
}
void RTPSender::SetRtpState(const RtpState& rtp_state) {
SetStartTimestamp(rtp_state.start_timestamp, true);
CriticalSectionScoped lock(send_critsect_.get());
sequence_number_ = rtp_state.sequence_number;
sequence_number_forced_ = true;