Update to spec 0.23.4

Except for Call stuff because the example using extensions needs
update to new spec.

1 files changed, 42 insertions, 3 deletions

diff --git a/spec/errors.xml b/spec/errors.xml
index a5271b5b6..7726f3cfd 100644
--- a/spec/errors.xml
+++ b/spec/errors.xml
@@ -386,6 +386,45 @@
     </tp:docstring>
   </tp:error>
 
+  <tp:error name="Media.Codecs Incompatible">
+    <tp:added version="0.23.4"/>
+    <tp:docstring>
+      Raised when the local streaming implementation has no codecs in common
+      with the remote side.
+
+      <tp:rationale>
+        This corresponds to
+        <tp:value-ref type="Call_State_Change_Reason">Media_Error</tp:value-ref>.
+      </tp:rationale>
+    </tp:docstring>
+  </tp:error>
+
+  <tp:error name="Media.Unsupported Type">
+    <tp:added version="0.23.4"/>
+    <tp:docstring>
+      The media stream type requested is not supported by either the
+      local or remote side.
+
+      <tp:rationale>
+        This corresponds to
+        <tp:value-ref type="Call_State_Change_Reason">Media_Error</tp:value-ref>.
+      </tp:rationale>
+    </tp:docstring>
+  </tp:error>
+
+  <tp:error name="Media.Streaming Error">
+    <tp:added version="0.23.4"/>
+    <tp:docstring>
+      Raised when the call's streaming implementation has some kind of internal
+      error.
+
+      <tp:rationale>
+        This corresponds to
+        <tp:value-ref type="Call_State_Change_Reason">Internal_Error</tp:value-ref>.
+      </tp:rationale>
+    </tp:docstring>
+  </tp:error>
+
   <tp:error name="Connection Refused">
     <tp:docstring>
       Raised when a connection is refused.
@@ -495,7 +534,7 @@
     <tp:added version="0.21.2"/>
     <tp:docstring>
       Raised when an incoming or outgoing <tp:dbus-ref
-      namespace="ofdT.Channel.Type">Call.DRAFT</tp:dbus-ref> is
+      namespace="ofdT.Channel.Type">Call1</tp:dbus-ref> is
       rejected by the the receiver.
     </tp:docstring>
   </tp:error>
@@ -537,7 +576,7 @@
         errors bad-format, invalid-xml, etc., which can't happen unless
         the local (or remote) XMPP implementation is faulty. This is
         also analogous to
-        <tp:type>Media_Stream_Error</tp:type>_Invalid_CM_Behavior,
+        <tp:value-ref type="Media_Stream_Error">Invalid_CM_Behavior</tp:value-ref>,
         <code>TP_DBUS_ERROR_INCONSISTENT</code> in telepathy-glib, and
         <code>TELEPATHY_QT4_ERROR_INCONSISTENT</code> in telepathy-qt4.
       </tp:rationale>
@@ -589,7 +628,7 @@
         to place a call or send a message.</p>
 
       <p>The key 'balance-required' MAY be included in
-        <tp:dbus-ref namespace="ofdT.Channel.Type.Call.DRAFT">CallStateDetails</tp:dbus-ref>
+        <tp:dbus-ref namespace="ofdT.Channel.Type.Call1">CallStateDetails</tp:dbus-ref>
         or a delivery report's <tp:type>Message_Part</tp:type>
         (with the same units and scale as
         <tp:dbus-ref namespace="ofdT.Connection.Interface.Balance">AccountBalance</tp:dbus-ref>)