If you want to depoly webrtc-agent in different regions, you can edit the "regions" (e.g. regions = [ "somewhere" ] ) in webrtc_agent/agent.toml. On the client side, specify "region" preference "somewhere" when creating token will make the matched-region webrtc-agent be used for a certain user.
If you want to move streams from one SFU to another, the current release does not support that.
Thank you for your reply. As you suggested, let us assume that we deploy two "webrtc-agents" in "Asia" and "Europe" regions. Also, User1 is located in "Asia" region, and User2 is located in "Europe" region. When the call is initiated, User1 will connects to "Asia" region "webrtc-agent" and User2 will connects to "Europe" region "webrtc-agent". Now, is it possible to establish the call between these two different "webrtc-agents"? If I understand your answer correctly, It is not possible. Am I correct? Please clarify.
For the case `When the call is initiated, User1 will connects to "Asia" region "webrtc-agent" and User2 will connects to "Europe" region "webrtc-agent"`
If User1 and User2 joined the same conference, the call will be established automatically between different webrtc-agents. And the internal connection between webrtc-agents will use TCP by default. So this case is supported.
What I mean is that if there are two different clusters (each has its own cluster-manager), users join different rooms in different clusters can not get streams from other cluster's webrtc-agent directly.
Yes, stream will spread across different webrtc-agents if publish and subscribe is not located in the same agent. Note, currently just 1 level cascading among webrtc-agent is supported.
So if we not mention region and isp in webrtc/agent.toml and we have multiple webrtc agents connected to single cluster manager does different clients from different region connects to all webrtc agents randomly or based on load it elects the webrtc agent? or its just connects to last used webrtc agent alone?
since right now from above scenario only one webrtc agent is getting utilzed.