I'm not sure I got you right. Especially about federation through subdomains. Is it "No, absolutely no, you can't save bandwidth"?
Well, I know only how 3 things works: first is an ordinary messaging. It's server-to-server, it's ok. Second is callings, and it's peer-to-peer, so there must be TURNs installed on both sides of VPN. And the last is Jitsi's conference / colibri, which is powered by... magic. There is smart-client, or "focus", which handles signaling and pass all the streams through itself, working as a TURN, am I right? And it's double-magic when we have two servers. What happens when I start up client, click "Create a video bridge" and select people from different servers? (PS we don't see each other, but our servers do).
Пятница, 3 марта 2017, 13:28 +06:00 от Saúl Ibarra Corretgé <email@example.com>:
On Mar 2, 2017, at 15:50, - - < firstname.lastname@example.org > wrote:
Hello, guys! You are doing a great job! Thanks for Jitsi and other cool and innovative things.
Just a simple question. Can I set up a configuration with two servers, like this:
( email@example.com --- JabberServer+VideoBridge) ------- vpn-------- (JabberServer2+VideoBridge2 --- firstname.lastname@example.org )
Is it possible in any way? Using desktop Jitsi or web-based "meet" app... Just for the sake of traffic reduction. As you understand, in case of single server all video streams in amount almost (N * N / 2) will go throung the vpn, and it's quite a lot....
You can connect multiple bridges to a single signaling server just fine, but conferences are scheduled on different bridges based on their load, and there is no way to change that.
You could use subdomains and leverage the fact that XMPP is federated to interconnect both infrastructures.