summaryrefslogtreecommitdiff
path: root/spec/Call_Stream_Interface_Media.xml
diff options
context:
space:
mode:
Diffstat (limited to 'spec/Call_Stream_Interface_Media.xml')
-rw-r--r--spec/Call_Stream_Interface_Media.xml36
1 files changed, 31 insertions, 5 deletions
diff --git a/spec/Call_Stream_Interface_Media.xml b/spec/Call_Stream_Interface_Media.xml
index 9e62c8744..54476f0fa 100644
--- a/spec/Call_Stream_Interface_Media.xml
+++ b/spec/Call_Stream_Interface_Media.xml
@@ -110,15 +110,41 @@
</tp:member>
</tp:mapping>
+ <tp:enum type="u" name="Stream_Component">
+ <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
+ Media 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">
<tp:docstring>The IP address to use.</tp:docstring>
</tp:member>
- <tp:member name="Port" type="q">
+ <tp:member name="Port" type="u">
<tp:docstring>The port number to use.</tp:docstring>
</tp:member>
<tp:member name="Info" type="a{sv}" tp:type="Candidate_Info">
@@ -133,7 +159,7 @@
signal them to the remote contact(s).
</tp:docstring>
<arg name="Candidates" direction="in"
- type="a(usqa{sv})" tp:type="Candidate[]">
+ type="a(usua{sv})" tp:type="Candidate[]">
<tp:docstring>
The candidates to be added.
</tp:docstring>
@@ -216,7 +242,7 @@
</property>
<property name="LocalCandidates" tp:name-for-bindings="Local_Candidates"
- type="a(usqa{sv})" tp:type="Candidate[]" access="read">
+ type="a(usua{sv})" tp:type="Candidate[]" access="read">
<tp:docstring>
[FIXME]. Change notification is via the
<tp:member-ref>LocalCandidatesAdded</tp:member-ref> signal.
@@ -229,7 +255,7 @@
Emitted when local candidates are added to the
<tp:member-ref>LocalCandidates</tp:member-ref> property.
</tp:docstring>
- <arg name="Candidates" type="a(usqa{sv})" tp:type="Candidate[]">
+ <arg name="Candidates" type="a(usua{sv})" tp:type="Candidate[]">
<tp:docstring>
Candidates that have been added.
</tp:docstring>