Lines Matching full:session
209 An example of an SRTP session using two rtpw programs follows:
247 in libSRTP. An RTP session is defined by a pair of destination
250 coordinate between the participants in an RTP session, e.g. to provide
251 feedback from receivers to senders. An @e SRTP @e session is
252 similarly defined; it is just an RTP session for which the SRTP
253 profile is being used. An SRTP session consists of the traffic sent
255 participant in a session is identified by a synchronization source
261 same session. The synchronization source identifier (SSRC) is used to
266 policy. Each stream within a session can have a distinct policy
267 applied to it. A session policy is a collection of stream policies.
269 A single policy can be used for all of the streams in a given session,
298 Within an SRTP session, there can be multiple streams, each
302 the state associated with an SRTP session. There can be multiple
306 participating in an SRTP session must have a stream context for each
307 source in that session, so that it can process the data that it
311 In libSRTP, a session is created using the function srtp_create().
312 The policy to be implemented in the session is passed into this
315 can also be linked together to form an entire session policy. A linked
316 list of srtp_policy_t structures is equivalent to a session policy.
326 streams in a session, but to use a distinct key for each stream. A
344 srtp_t session;
361 // allocate and initialize the SRTP session
362 srtp_create(&session, policy);
370 srtp_protect(session, rtp_buffer, &len);
