From 744335987b0015ee55836752674b319e43a78679 Mon Sep 17 00:00:00 2001 From: epoberezkin Date: Fri, 23 Oct 2026 09:07:15 +0000 Subject: [PATCH] deploy: 31c4b681898173a127d472650646f976701c04df --- docs/protocol/simplex-chat.html | 2 +- docs/protocol/simplex-chat.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/protocol/simplex-chat.html b/docs/protocol/simplex-chat.html index 109badce0a..87b6793d5b 100644 --- a/docs/protocol/simplex-chat.html +++ b/docs/protocol/simplex-chat.html @@ -1075,7 +1075,7 @@ eventWord = 1* ALPHA

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.

  • -

    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.

    +

    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.

  • x.call.end message is sent to notify the other party that the call is terminated.

    diff --git a/docs/protocol/simplex-chat.md b/docs/protocol/simplex-chat.md index 7da0aeafac..ff9fcfa7e1 100644 --- a/docs/protocol/simplex-chat.md +++ b/docs/protocol/simplex-chat.md @@ -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.