Skip to content

Commit

Permalink
Fix rendering errors: remove duplicate section and unexpected svg sty…
Browse files Browse the repository at this point in the history 
…le attributes.
  • Loading branch information
@HansBusch
HansBusch committed Jul 1, 2024
1 parent 7251298 commit 8471259
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 91 deletions.
87 changes: 0 additions & 87 deletions doc/WebRTC.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -578,93 +578,6 @@
</tgroup>
</table>
</section>
<section xml:id="section_error_notification">
<title>error</title>
<para>An ONVIF compliant signaling server, device and client shall support sending or receiving notifications signaling that an error has occurred.</para>
<para>This message is a [JSON-RPC] "Request notification" and shall include [JSON-RPC] "Error object" in its <literal>params</literal> field.</para>
<variablelist role="op">
<varlistentry>
<term>request</term>
<listitem>
<para role="param">code [int]</para>
<para role="text">A number that indicates the error type that occurred.</para>
<para role="param">message [string]</para>
<para role="text">A string providing a short description of the error. The message should be limited to a concise single sentence.</para>
<para role="param">session [string]</para>
<para role="text">The ID assigned by the signaling server to the session. </para>
</listitem>
</varlistentry>
<varlistentry>
<term>response</term>
<listitem>
<para role="text">&lt;none&gt;</para>
</listitem>
</varlistentry>
<varlistentry>
<term>faults</term>
<listitem>
<para role="text">&lt;none&gt;</para>
</listitem>
</varlistentry>
</variablelist>
<para>The following table defines possible error codes:</para>
<table>
<title>WebRTC signaling errors</title>
<tgroup cols="3">
<colspec colname="c1" colwidth="49*" />
<colspec colname="c2" colwidth="13*" />
<colspec colname="c3" colwidth="37*" />
<thead>
<row>
<entry>
<para>Signaling Error</para>
</entry>
<entry>
<para>Error Code</para>
</entry>
<entry>
<para>Reason</para>
</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry>
<para>Insufficient resources</para>
</entry>
<entry>
<para>1001</para>
</entry>
<entry>
<para>The peer does not have sufficient resources.</para>
</entry>
</row>
<row>
<entry>
<para>Peer disconnected</para>
</entry>
<entry>
<para>1002</para>
</entry>
<entry>
<para>A peer in the session has closed its websocket connection with the Signaling Server.</para>
</entry>
</row>
<row>
<entry>
<para>Malformed candidate</para>
</entry>
<entry>
<para>1003</para>
</entry>
<entry>
<para>The trickle ICE candidate received is malformed.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>Example Flow (informative)</title>
<para>The following example shows the flow using JSON-RPC 2.0. Note that for improved
Expand Down
8 changes: 4 additions & 4 deletions doc/media/WebRTC/webrtc_signaling_flow.svg
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 8471259

Please sign in to comment.