Is there a clean migration path from RTP to SRTP?

[Sebastian Dröge]

On Di, 2016-07-26 at 15:47 -0700, Andres Gonzalez wrote:
> Thank you Sebastian for your response. I was going down the wrong rabbit hole
> so that helps.
> 
> I have looked at the rtsp-server code and I can see its use of the
> request-rtp-encoder/decoder signals for connecting the srtp GstElement to a
> pipeline.  However, I do not understand that code base well enough to
> understand how to actually use srtpenc and srtpdec in my own existing
> GStreamer rtp pipelines.
> 
> It appears that using srtpenc/srtpdec elements is very different from other
> GStreamer elements which follow a pattern of linking various processing
> elements together in a serial pipeline. Since they are not manually linked
> in the pipeline like other elements, I am at a loss as to how to migrate my
> RTP pipelines to use SRTP.
> 
> Question: Is there any example code available on how to specifically use the
> srtpenc and srtpdec elements?

I'm not aware of any, sorry. But the basic idea is that instead of
linking them in the pipeline yourself, you just provide them to rtpbin
via those signals when needed and it will link it at the appropriate
places.

Apart from that the element usage is exactly the same, you set the
properties and connect to the signals as usual.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160727/fca7d646/attachment.sig>