Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable-20.0] Add support for federated calls #4207

Merged
merged 11 commits into from
Sep 13, 2024

Conversation

backportbot[bot]
Copy link

@backportbot backportbot bot commented Sep 13, 2024

Backport of PR #4120

danxuliu and others added 11 commits September 13, 2024 15:01
Starting with Talk 20 the signaling settings include a "federation"
property that provide the values needed to join a federated room in the
external signaling settings. The "federation" property is specific to
each conversation, and it will be returned although empty for
non-federated conversations.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
This is necessary to get the specific federation properties for the
room.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
The "federation" values are used by the external signaling server to
establish a connection with the remote signaling server in a federated
room.

For now this is applied only in calls; when the room is joined in the
chat view again after a call it will still join it in the old way,
without federation properties, which will cause the connection with the
remote signaling server to be closed.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Starting with Talk 20 the signaling messages that provide updates to the
participants ("participants->update" in the external signaling server,
"usersInRoom" in the internal signaling server) now include "actorType"
and "actorId" properties for each participant.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Otherwise the WebSocket configuration and session clashes with the one
from the CallActivity, which already uses the federated settings.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Marcel Hibbe <[email protected]>
@backportbot backportbot bot requested review from mahibi and danxuliu September 13, 2024 15:01
@backportbot backportbot bot added enhancement New feature or request 3. to review Waiting for reviews feature: ☎️ call feature: 🌐 federation Support for federated conversations labels Sep 13, 2024
@backportbot backportbot bot added this to the 20.0.0 milestone Sep 13, 2024
@mahibi mahibi merged commit 32ed934 into stable-20.0 Sep 13, 2024
9 of 15 checks passed
@mahibi mahibi deleted the backport/4120/stable-20.0 branch September 13, 2024 15:02
Copy link
Contributor

Codacy

Lint

TypemasterPR
Warnings8694
Errors131131

SpotBugs

CategoryBaseNew
Bad practice66
Correctness1111
Dodgy code7879
Internationalization33
Malicious code vulnerability33
Performance66
Security11
Total108109

Lint increased!

SpotBugs increased!

Copy link
Contributor

APK file: https://www.kaminsky.me/nc-dev/android-artifacts/4207-talk.apk

qrcode

To test this change/fix you can simply download above APK file and install and test it in parallel to your existing Nextcloud Talk app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews enhancement New feature or request feature: ☎️ call feature: 🌐 federation Support for federated conversations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants