Skip to content

Commit a68b019

Browse files
authored
Update detailed-call-flows.md
1 parent b9a39cf commit a68b019

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communication-services/concepts/detailed-call-flows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Call flows in Azure Communication Services calling SDK and Teams clients are bas
4040

4141
Media traffic is encrypted, and flows between, the caller and callee using Secure RTP (SRTP), a profile of Real-time Transport Protocol (RTP) that provides confidentiality, authentication, and replay attack protection to RTP traffic. In most cases, client to client media traffic is negotiated through client to server connection signaling, and is encrypted using SRTP when going directly from client to client.
4242

43-
Azure Communication Services calling SDK and Teams use DTLS to derive an encryption key based on per-call keys generated on both client endpoints. Since DTLS derives the key based on the client certificates, the key is opaque to Microsoft. Once the handshake is done, the media begins to flow using this DTLS-negotiated encryption key over SRTP.
43+
Azure Communication Services calling SDK use DTLS to derive an encryption key. Once the DTLS handshake is done, the media begins to flow using this DTLS-negotiated encryption key over SRTP.
4444

4545
Azure Communication Services calling SDK and Teams clients uses a credentials-based token for secure access to media relays over TURN. Media relays exchange the token over a TLS-secured channel.
4646

0 commit comments

Comments
 (0)