Talk video chat with federated vs. guest participants

Greetings All:

Struggling with federated calls in Talk. Using AIO on both servers, I can successfully configure trusted servers:

Now, If I create a new conversation and enable “Guests are allowed to join this conversation via link”

… I can share that link and the two of us can experience a successful video call. However, If I create a new conversation and add the other person via his federated ID, I can chat and share files, but can’t establish a successful video call with him. It continues to fail. Having him simply click the ‘shared link’ works without any issues.

I’ve looked at the following docs link - Advanced Talk features — Nextcloud latest User Manual latest dokumentacija

… and see the following within:

" Federated conversation

With Federation feature, users can create conversations across different federated Talk instances and use Talk features as if they were on a same server.

Important Under current development. Basic chat features are available, more to come in the future!"

Any thoughts? Why would it work with sharing the conversation link, but not if I create a conversation and add him via the federated user add?

Thanks much,

Andy

Any ideas here?

Not a Talk Expert, i’m using it on a single instance, not AIO, and i run a Talk HPB on a separate server for better performance in group meetings.

My best guess to your problem would be that each instance uses it’s own instance of the included Talk backend. If you share a link to a conversation on one instance, all users will connect to this instance, locals with their account, ‘foreigners’ as guests, but it is one conversation on one instance. Whilst the federation invite does create a conversation on the opposite instance for their users and then connects the two conversations. The difference is that invited guests use the Talk app and configuration of the host instance and federated users connect to their own Talk app and config.

Perhaps a more experienced Talk admin can comment on the idea if configuring both Nextcloud instances to use the same Talk backend would help.

Very interesting and logically makes sense to me. Thanks for the input here.

Maybe … just maybe ‘they’ are waiting for Nextcloud Talk Munich :wink: as there will be some sort of amazing update.

Sometimes it simply requires reading …

“Federated chats have several limitations … or make video calls.”

Not a supported method of using Talk.

1 Like

I stand corrected … again. Learning is such a wonderful thing :slight_smile:

Using Matterbridge, Federated Calls are supported and I now have it working between two AIO instances with different FQDNs.

  1. Installed the ‘Talk Matterbridge’ app in NC each instance
  2. Enabled Federated in Talk App in > Talk admin settings
  3. Enabled Matterbridge integration in > Talk admin settings
  4. For specific ‘conversations’, Enable bridge.
  5. ‘bridge-bot’ is added to the conversation and i can now have video calls with federated users

This looks suspiciously simple. I can’t believe it. :laughing: :laughing:
Don’t take me wrong, I mean it as a joke. :tada:

I would definitely appreciate your possible experience with the functionality.

I have two AIO’s presently that I am testing with federated talk … in my environment. Later today I am federating with a close colleague who also has AIO who I’ve been historically testing with. Will validate it further. Post that further testing, I’m happy to discuss in more detail the working configuration and can jump on a call if desired to talk (no pun) through it as well.

2 Likes

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.