Browse Source
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>pull/4952/head
5 changed files with 23 additions and 1 deletions
Loading…
Reference in new issue