Changes between Version 3 and Version 4 of SRTP

Timestamp:

Jan 23, 2008 6:49:30 PM (16 years ago)

Author:

bennylp

Comment:

--

SRTP

@@ -55 +55 @@
 === pjmedia_transport_srtp Implementation ===
 
-As we know, media transport is separated from the stream object (which does the encoding/decoding of PCM frames, (de)packetization of RTP packets, and de-jitter buffering). The connection between stream and media transport is established when the stream is created (because during stream creation we need to specify media transport), and the interconnection can be depicted from the diagram below:
+As we know, media transport is separated from the stream object (which does the encoding/decoding of PCM frames, (de)packetization of RTP/RTCP packets, and de-jitter buffering). The connection between stream and media transport is established when the stream is created (we need to specify media transport during stream creation), and the interconnection can be depicted from the diagram below:
 
+[[Image(media-transport.PNG)]]
 
+I think the diagram above is self-explanatory.
 
+With SRTP, the SRTP is implemented as some kind of "adapter", which is plugged between the stream and the actual media transport that does sending/receiving RTP/RTCP packets. When SRTP is used, the interconnection between stream and transport is like the diagram below:
 
+[[Image(media-srtp-transport.PNG)]]
 
+So to stream, the SRTP transport behaves as if it is a media transport (because it '''is''' a media transport), and to the media transport it behaves as if it is a stream. The SRTP object will forward RTP packets back and forth from stream to the actual transport and vice versa, encrypting/decrypting the RTP/RTCP packets as necessary.
 
-
+The neat thing about this design is the SRTP "adapter" then can be used to encrypt any kind of media transports. We currently have UDP and ICE media transports that can benefit SRTP, and we could add SRTP to any media transports that will be added in the future.
 
 ----
@@ -71 +76 @@
 === Using SRTP in PJSUA-LIB ===
 
+The use of SRTP is controlled by settings in both pjsua_config and pjsua_acc_config. The settings in pjsua_config specifies the default settings for all accounts, and the settings in pjsua_acc_config can be used to further set the behavior for that specific account.
+
+In both pjsua_config and pjsua_acc_config, there are two configuration items to control:
+
+ '''use_srtp'''::
+  This option controls whether secure media transport (SRTP) should be used for this account. Valid values are:
+   - PJMEDIA_SRTP_DISABLED (0): SRTP is disabled, and incoming call with RTP/SAVP transport will be rejected.
+   - PJMEDIA_SRTP_OPTIONAL (1): SRTP will be advertised and SRTP will be used if remote supports it, but the call may fall back to unsecure media.
+   - PJMEDIA_SRTP_MANDATORY (2): secure media is mandatory, and the call can only proceed if secure media can be established.
+  The default value for this option is PJSUA_DEFAULT_USE_SRTP, which is zero (disabled).
+
+ '''srtp_secure_signaling'''::
+  This option controls whether SRTP requires secure signaling to be used. This option is only used when {{{use_srtp}}} option above is non-zero. Valid values are:
+     - 0: SRTP does not require secure signaling
+     - 1: SRTP requires secure transport such as TLS
+     - 2: SRTP requires secure end-to-end transport (SIPS)
+  The default value for this option is PJSUA_DEFAULT_SRTP_SECURE_SIGNALING, which is 1 (require TLS transport).
+
+
+
+
+=== pjsua ===
+
+New option '''---use-srtp''' is added, with valid values are 0, 1, or 2. This corresponds to {{{use_srtp}}} setting above.
+
+Sample usage:
+{{{
+ $ ./pjsua --use-tls --use-srtp=1
+}}}
+
+Note: we need to enable TLS since by default SRTP requires secure signaling to be used (see ''srtp_secure_signaling'' setting above). If you want to use SRTP with non-secure transport (which is not recommended unless for testing purpose only!), you can modify ''srtp_secure_signaling'' setting in pjsua application.
+
+
 === Using SRTP Transport Directly ===
+
+The SRTP transport may also be used directly without having to involve SDP negotiations. However, you will need to have a different mechanism to exchange keys between endpoints.
+
+To use SRTP transport directly:
+ - Call pjmedia_transport_srtp_create() to create the SRTP adapter, giving it the actual media transport instance (such as UDP transport).
+ - Call pjmedia_transport_srtp_start() to active SRTP session, giving it both local and remote crypto settings and keys.
+ - Call pjmedia_transport_attach() to configure the remote RTP/RTCP addresses and attach your RTP and RTCP callbacks.
+ - Call pjmedia_transport_send_rtp() and pjmedia_transport_send_rtcp() to send RTP/RTCP packets.
+ - Once you done with your session, call pjmedia_transport_close() to destroy the SRTP adapter (and optionally the actual transport which is attached to the SRTP adapter, depending on whether ''close_member_tp'' flag is set in the options when creating the SRTP adapter).