dandri/simplex-chat
1
0 Fork 0
mirror of https://github.com/simplex-chat/simplex-chat.git synced 2026-10-25 14:43:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 31c4b68189

Browse Source
This commit is contained in:
epoberezkin committed 2026-10-23 09:07:15 +00:00
1 parent 797b052d6a
commit 744335987b
2 files changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/protocol/simplex-chat.html
+1 -1
View File
@@ -1075,7 +1075,7 @@ eventWord = 1* ALPHA
<p><code>x.call.answer</code>: to continue with call connection the initiating clients must reply with <code>x.call.answer</code> message. This message contains WebRTC answer and collected ICE candidates. Additional ICE candidates can be sent in <code>x.call.extra</code> message.</p>
</li>
<li>
<p><code>x.call.extra</code> with <code>rtcSession</code> property: when an established connection is lost, the client that sent <code>x.call.offer</code> restarts ICE and sends the new offer in <code>rtcSession</code> of <code>x.call.extra</code>. The other client replies with the answer in <code>rtcSession</code> of <code>x.call.extra</code>. Clients that do not support it ignore this property, and the call ends when reconnection times out.</p>
<p><code>x.call.extra</code> with <code>rtcSession</code> property: when an established connection is lost, the client that sent <code>x.call.offer</code> restarts ICE and sends the new offer in <code>rtcSession</code> of <code>x.call.extra</code>. The other client replies with the answer in <code>rtcSession</code> of <code>x.call.extra</code>. Clients restart ICE only when the peer supports chat protocol version 22 or later, otherwise the call ends when the connection is lost.</p>
</li>
<li>
<p><code>x.call.end</code> message is sent to notify the other party that the call is terminated.</p>
docs/protocol/simplex-chat.md
+1 -1
View File
@@ -282,7 +282,7 @@ These message are used for WebRTC calls:
3. `x.call.answer`: to continue with call connection the initiating clients must reply with `x.call.answer` message. This message contains WebRTC answer and collected ICE candidates. Additional ICE candidates can be sent in `x.call.extra` message.
4. `x.call.extra` with `rtcSession` property: when an established connection is lost, the client that sent `x.call.offer` restarts ICE and sends the new offer in `rtcSession` of `x.call.extra`. The other client replies with the answer in `rtcSession` of `x.call.extra`. Clients that do not support it ignore this property, and the call ends when reconnection times out.
4. `x.call.extra` with `rtcSession` property: when an established connection is lost, the client that sent `x.call.offer` restarts ICE and sends the new offer in `rtcSession` of `x.call.extra`. The other client replies with the answer in `rtcSession` of `x.call.extra`. Clients restart ICE only when the peer supports chat protocol version 22 or later, otherwise the call ends when the connection is lost.
5. `x.call.end` message is sent to notify the other party that the call is terminated.