Consider RTP & RTCP as a new transport protocol

[stv0g]

• https://en.wikipedia.org/wiki/Real-time_Transport_Protocol
• https://www.ietf.org/proceedings/67/slides/avt-1.pdf
• https://csperkins.org/standards/ietf-64/2005-11-10-IETF64-DCCP-rtp-dccp.pdf
• https://tools.ietf.org/html/rfc5762
• https://tools.ietf.org/html/rfc4340

[stv0g]

See also: https://tools.ietf.org/html/rfc8085#section-3.1

[stv0g]

Hi @marvinklimke,

I found this older issue about adding RTP/RTCP support to VILLASnode. Its already roughly a year old :smile:

[stv0g]

Here is my current list of RTP libraries which might be suitable:

RTP Stacks:

• https://github.com/creytiv/re
• https://gstreamer.freedesktop.org/documentation/rtp.html
• https://www.gnu.org/software/ccrtp/
• http://www.linphone.org/technical-corner/ortp/overview
• https://github.com/j0r1/JRTPLIB
• https://www.pjsip.org/

Tools

• http://www.cs.columbia.edu/irt/software/rtptools/

Other lists and overviews:

• https://docs.huihoo.com/telecom/sip_rtp_stack.html
• http://www.pernau.at/kd/voip/bookmarks-rtp-stacks.html

[stv0g]

Lateron, I would suggest using Wireshark as a packet analysis tool for checking the RTP traffic.

[stv0g]

In particular, I like the libre library because it seems to support a wide range of real-time communication protocols.

@marvinklimke could you do some research which of these RTP stacks

• is currently under active development (last commit within 2017/8)
• has a C API or C binding
• is generic enough to be used with our own RTP profiles

[stv0g]

In GitLab by @marvinklimke on Nov 2, 2018, 11:58

Hello!

I did some basic research on the mentioned RTP stacks and listed my findings below.

libre

• development: active (numerous commits in 2018)
• implementation: C
• generic and modular
• many additional protocols implemented
• clean and readable code

GStreamer

• development: active (multiple releases in 2018)
• no public repository (?)
• implementation: C (OOP using GLib)

ccRTP

• development: stagnant (last commit in 2015)
• implementation: C++ (no official C bindings)
• relatively specific to VoIP applications (GNU Telephony)

oRTP

• development: active (numerous commits in 2018)
• implementation: C
• sufficiently generic (media streaming in separate lib)

JRTPLIB

• development: active (some commits in 2018)
• implementation: C++ (no official C bindings)
• relatively complex, event-based api

PJSIP

• development: active (last release in 2018)
• implementation: C++
• relatively specific to VoIP applications (SIP)

Personal Opinion

I think libre is the way to go here. The library is actively developed and the modular and clear code style allows for a (hopefully) quick and smooth incorporation. The additional protocols are nice to investigate later on.

---

@stvogel do you remember to send me a copy of the master thesis that we talked about during our meeting? Also, I am going to investigate libre a bit deeper until we figure out the issue with villas on my machine, if that's fine with you.

[stv0g]

@marvinklimke

I also like libre

There is also a repo with some example applications: https://github.com/creytiv/redemo However the documentation is quite sparse.. And there are no examples for RTP/RTCP.

I think we still might want to use it. However, you would need to read the libre code to actually understand it :D

[stv0g]

marked this issue as related to #218

[stv0g]

marked this issue as related to #215

[stv0g]

The basic RTP node-type has been merged into version v0.7.0 of VILLASnode.

[stv0g]

closed