diff options
| author | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2021-01-13 13:05:32 +0300 |
|---|---|---|
| committer | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2021-01-14 15:47:40 +0300 |
| commit | deb2494193a51321273070b39739e625651d40ea (patch) | |
| tree | 4f8637bda228d9b4bdcf3918af0e314f457a06b0 /docs | |
| parent | fd6b42e12c16a4f25d74ad243b815234fc5f5986 (diff) | |
Send Nextcloud session id too when a participant joins a call
When the internal signaling server is used the Nextcloud session id and
the signaling session id are the same. However, if the external
signaling server is used they are different.
Signaling messages for participants in calls (like joining the call,
muting and so on) are identified only by their signaling session id, so
when the external signaling server is used it was not possible to
associate participants in calls with the participant information
provided by the Nextcloud server.
However, when a participant joins a call her client notifies the
Nextcloud server (either directly or, in the case of SIP clients,
through the signaling server). The Nextcloud server then notifies the
signaling server which, in turn, notifies all the clients. When
Nextcloud notifies the signaling server the participant is identified
with the Nextcloud session id, and the signaling server then replaces
that with the signaling session id before relaying the message to the
clients.
Due to this when a participant joins (or leaves) a call now the
Nextcloud session id is sent too in an extra property. This property is
not adjusted by the external signaling server, so the clients receive
both the signaling session id and the Nextcloud session id and thus are
able to map them.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/standalone-signaling-api-v1.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/standalone-signaling-api-v1.md b/docs/standalone-signaling-api-v1.md index 8cfffc49b..f98e84169 100644 --- a/docs/standalone-signaling-api-v1.md +++ b/docs/standalone-signaling-api-v1.md @@ -549,7 +549,9 @@ Message format (Server -> Client, participants change): If a participant has the `inCall` flag set, he has joined the call of the room and a WebRTC peerconnection should be established if the local client is also -in the call. +in the call. In that case the participant information will contain properties +for both the signaling session id (`sessionId`) and the Nextcloud session id +(`nextcloudSessionId`). ## Room messages |