Lines Matching refs:dtls
257 // When using DTLS-SRTP, we must reset the SrtpFilter every time the transport
258 // changes and wait until the DTLS handshake is complete to set the newly
262 // DTLS-SRTP when the writable_ becomes true again.
350 << "Setting RTCP for DTLS/SRTP after SrtpFilter is active "
522 // state, setting up DTLS-SRTP context is deferred to ChannelWritable_w to
524 // TransportChannel) or when TransportChannel is attached after DTLS is
740 // b) we got SRTP packets before DTLS completed on both the RTP and RTCP
741 // channels, so we haven't yet extracted keys, even if DTLS did complete
866 // Since DTLS is applied to all channels, checking RTP should be enough.
870 // This function returns true if either DTLS-SRTP is not in use
871 // *or* DTLS-SRTP is successfully set up.
883 LOG(LS_ERROR) << "No DTLS-SRTP selected crypto suite";
887 LOG(LS_INFO) << "Installing keys from DTLS-SRTP on "
891 // OK, we're now doing DTLS (RFC 5764)
900 LOG(LS_WARNING) << "DTLS-SRTP key export failed";
905 // Sync up the keys with the DTLS-SRTP interface
951 LOG(LS_WARNING) << "DTLS-SRTP key installation failed";
1016 // |dtls| will be set to true if DTLS is active for transport channel and
1019 bool* dtls,
1021 *dtls = transport_channel_->IsDtlsActive();
1022 if (*dtls && !cryptos.empty()) {
1023 SafeSetError("Cryptos must be empty when DTLS is active.",
1039 bool dtls = false;
1040 ret = CheckSrtpConfig(cryptos, &dtls, error_desc);
1046 // If DTLS is already active on the channel, we could be renegotiating
1048 if (!dtls) {
1053 // If we're doing DTLS-SRTP, we don't want to update the filter
1055 if (!dtls) {
1060 // If we're doing DTLS-SRTP, we don't want to update the filter
1062 if (!dtls) {
2057 // SCTP or DTLS.
