<HTML><BODY><div>
<div>
<pre class="result--content--pre" style="-webkit-text-stroke-width:0px; color:#000000; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; letter-spacing:normal; line-height:1.2em; margin-bottom:0px; margin-left:0px; margin-right:0px; margin-top:0px; orphans:2; overflow:hidden; padding:0px; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; user-select:text; widows:2; word-spacing:0px">Hi list
I’m trying to find the best solution for setting
federated user location cluster.
Key notes:
- geographically distributed OpenSIPS nodes
- the same numbering plan for all devices (no strict
ranges for Europe/Asia and so on)
- ability to be in service (at least inside of each node)
in case of short periodic connectivity problems.
I configured (in VirtualBox test environment) 2 nodes with
one MongoDB instance, using this tutorial:
<a href="https://www.opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation">https://www.opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation
</a>It works fine.
But I’d like to add some extra high-availability for situations if
there will be some problems with connectivity between nodes.
At least to achieve the ability of each node to serve calls among
those users who are registered directly on it.
What is the best architecture? Maybe something else, not MongoDB?
user1 user4
| |
| |
+-----------+ +-----------+
| osips1 | | osips2 |
user2------- | Europe |<------------------------->| Asia |----user5
+-----------+ +-----------+
| |
| |
| user6
user3
</pre>
</div>
<div> </div>
<div data-signature-widget="container">
<div data-signature-widget="content">
<div>-----------------------------------------------<br>
<span style="font-size: 15px;">BR, Alexey</span></div>
</div>
</div>
</div>
</BODY></HTML>