Fix the issues in SrtpTransport.

In SrtpTransport::SetRtcpParams, send_rtcp_session_ should really call
SetSend rather than SetRecv.

Modified the LOG message in SrtpTransport::SetRtpParams.

Bug: webrtc:8436
Change-Id: Iccbfbc5ef2d4f4ebd5f876c3f6dcc81671fdc631
Reviewed-on: https://webrtc-review.googlesource.com/14562
Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org>
Commit-Queue: Zhi Huang <zhihuang@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#20403}
This commit is contained in:
Zhi Huang 2017-10-22 16:17:47 -07:00 committed by Commit Bot
parent a17ce27b20
commit ef48df9aeb

View File

@ -204,7 +204,7 @@ bool SrtpTransport::SetRtpParams(int send_cs,
return false;
}
LOG(LS_INFO) << "SRTP " << (new_sessions ? "updated" : "activated")
LOG(LS_INFO) << "SRTP " << (new_sessions ? "activated" : "updated")
<< " with negotiated parameters:"
<< " send cipher_suite " << send_cs << " recv cipher_suite "
<< recv_cs;
@ -225,7 +225,7 @@ bool SrtpTransport::SetRtcpParams(int send_cs,
}
send_rtcp_session_.reset(new cricket::SrtpSession());
if (!send_rtcp_session_->SetRecv(send_cs, send_key, send_key_len)) {
if (!send_rtcp_session_->SetSend(send_cs, send_key, send_key_len)) {
return false;
}