Hi, Ewgeny!
The usrloc binary replication is only the first step in the direction of
an horizontally scalable OpenSIPS cluster. It is designed to provide a
hot-backup registrar, through the use of a Virtual IP.
To answer your questions:
1) with usrloc binary replication, if the primary machine reboots, the
VIP will automatically switch over to the hot backup, and the SIP
registrar solution will continue to work. Once server 1 comes back
online (in secondary mode) it will gradually become up-to-date with
server 2 (current primary), within a couple of hours.
2) dialog replication is currently implemented in a similar manner, with
a hot backup, and no need for an SQL database in order to keep real-time
information.
We are currently working on providing a distributed SIP registrar
solution in the upcoming OpenSIPS 2.2 LTS. You can read some of the
discussions around it here [1]. Questions / suggestions are welcome!
[1]: http://www.opensips.org/Community/IRCmeeting20150527
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 29.02.2016 16:06, [email protected] wrote:
Hi !
It's really nice option - that now Opensips nodes can replicate "SIP
registrations" and "Dialogs" between each other w *"bin_listen" options.
http://www.opensips.org/Documentation/Interface-Binary-2-1
*
I have a few question related to cluster architecture with fail over:
1).
- If one of the "Opensips phone edges" was restarted - can it catch
all USRLOC registrations through binary interface from alive nodes ?
- if it can't do restoring of the database through binary interface -
maybe you have an idea how to do that ?
2).
- it's share dialogs information - if one node is suddenly down, can
call dialog be proceeded on other node ?
With kind regards,
Ewgeny Berladin
Voip Engineer
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
