summaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorDavid Laban <david.laban@collabora.co.uk>2011-01-25 16:23:51 +0000
committerDavid Laban <david.laban@collabora.co.uk>2011-01-25 16:23:51 +0000
commit6c8f4904d3f2b7942ad76dc0d2a7edc7daf14c58 (patch)
tree7017615c06a80f4fe8dd9b87c609d42badec6ded /spec
parent7929cf4016d44cd5484ecd921f0f1650315a40ab (diff)
Update to spec master (Stream_Component enum)
Diffstat (limited to 'spec')
-rw-r--r--spec/Call_Stream_Interface_Media.xml28
1 files changed, 27 insertions, 1 deletions
diff --git a/spec/Call_Stream_Interface_Media.xml b/spec/Call_Stream_Interface_Media.xml
index 21255ab..dffb0a4 100644
--- a/spec/Call_Stream_Interface_Media.xml
+++ b/spec/Call_Stream_Interface_Media.xml
@@ -110,9 +110,35 @@
</tp:member>
</tp:mapping>
+ <tp:enum type="u" name="Stream_Component">
+ <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
+ RTP streams can use more than one UDP socket: one for RTP (data)
+ and one for RTCP (control). Most of the time, they are adjacent
+ to each other, but some protocols (xmpp) signal each port separately.
+ </tp:docstring>
+ <tp:enumvalue suffix="Unknown" value="0">
+ <tp:docstring>
+ The stream transport type is unknown or not applicable
+ (should not appear over dbus).
+ </tp:docstring>
+ </tp:enumvalue>
+ <tp:enumvalue suffix="Data" value="1">
+ <tp:docstring>
+ This is the high-traffic data socket, containing the audio/video
+ data for the stream.
+ </tp:docstring>
+ </tp:enumvalue>
+ <tp:enumvalue suffix="Control" value="2">
+ <tp:docstring>
+ This is the low-traffic control socket, usually containing feedback
+ about packet loss etc.
+ </tp:docstring>
+ </tp:enumvalue>
+ </tp:enum>
+
<tp:struct name="Candidate" array-name="Candidate_List">
<tp:docstring>A Stream Candidate.</tp:docstring>
- <tp:member name="Component" type="u">
+ <tp:member name="Component" type="u" tp:type="Stream_Component">
<tp:docstring>The component number.</tp:docstring>
</tp:member>
<tp:member name="IP" type="s">