[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Linphone-developers] [PATCH] DCCP Support

From: Samuel Jero
Subject: [Linphone-developers] [PATCH] DCCP Support
Date: Tue, 11 Jun 2013 17:53:39 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6

As part of my masters work, I have added support for streaming media
over the Datagram Congestion Control Protocol (DCCP) to linphone. DCCP
is a relatively new protocol (2006) developed by the IETF to provide
congestion control without reliability for applications like VoIP and
video streaming (RFC4340-- I would
like to contribute this work back to the main Linphone code-base, if
possible, so that others can utilize it.

My patches consist of three main parts:
1)Adding support for DCCP to oRTP. This involves substantial changes to
rtpsession_inet.c, particularly since DCCP is a connection-oriented
protocol, unlike UDP.
2)Updating the bitrate control mechanisms in mediastreamer2 and the
feedback it receives from oRTP. DCCP provides feedback to the
application as to how fast it is allowed to send and when it needs to
slow down. This feedback is distinctly more rapid that RTCP reports, so
I utilize it in preference to RTCP for bitrate control.
3)Updating APIs throughput oRTP, mediastreamer2, and liblinphone to
allow selection of transport protocol.

As the patches to add DCCP support are fairly significant, I have
created a repository on github containing the changes:
oRTP: git://   branch: for-linphone
git://   branch:
linphone: git://   branch: for-linphone
These branches base off of the master branch from
git:// as of 2013-06-10.

Direct links to my commits are below:

Any comments on these patches would be appreciated. I can try to split
out a large number of smaller patches if that would help, but a lot of
the changes are interrelated.


Samuel Jero
Masters Student
Computer Science
Internetworking Research Group
Ohio University

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]