3.1.5.5.6 Interaction Between Audio/Video and Data Encryption Negotiation
Although data collaboration and audio/video encryption are negotiated separately and controlled through separate registry settings at the client, in a session that involves both DC and audio/video, both parties can negotiate encryption for one type but not for the other.
The following example shows how different encryption settings could be requested for audio/video and data collaboration; however, in this example, the session fails.
-
m=audio 49170 RTP/AVP 0 a=encryption:required k=base64:bhdsfsd78f7dssdfssfsd7sdfssa m=video 49171 RTP/AVP 25 a=encryption:required k=base64:bhdsfsd78f7dssdfssfsd7sdfssa m=application 1503 tcp msdata a=encryption:rejected
For the session to succeed, encryption must be successfully negotiated for all media types in that session.
For reINVITEs, failure to negotiate encryption does not result in failure of the existing session. As with any 4xx or 5xx response to a reINVITE, the client reverts to the previous session description, including any encryption parameters that were negotiated at that time.