Hi Volga,
The 2.4 dialog clustering definitely supports "active-active" setups.
For this, you will need to use two virtual IPs, each being primary for
one of the nodes, such that you avoid those "dialog created on unknown
IP" errors when replicating dialogs to the backup node.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 16.08.2018 08:02, volga...@networklab.ca wrote:
Hello Everyone,
Based on this thread
https://opensips.org/pipermail/users/2014-August/029635.html dialog
replication is not design for active/active scanario. My question when
federated no sql cluster enabled is it really need it ?
tried enable and getting errors
Aug 15 23:42:22 aitossbc01 /usr/sbin/opensips[12909]:
WARNING:dialog:fetch_socket_info: non-local socket <udp:opensips
public ip:5060>...ignoring
Aug 15 23:42:22 aitossbc01 /usr/sbin/opensips[12909]:
ERROR:dialog:dlg_replicated_create: Replicated dialog doesn't match
any listening sockets
Aug 15 23:42:22 aitossbc01 /usr/sbin/opensips[12909]:
ERROR:dialog:receive_dlg_repl: Failed to process a binary packet!
#### Dialog
loadmodule "dialog.so"
modparam("dialog", "db_url", "postgres://")
modparam("dialog", "db_mode", 1)
modparam("dialog","profiles_with_value","outbound; inbound")
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 3600)
modparam("dialog", "options_ping_interval", 900)
modparam("dialog", "profiles_with_value", "caller ; domain")
modparam("dialog", "dialog_replication_cluster", 1)
modparam("dialog", "profile_replication_cluster", 1)
modparam("dialog", "dlg_sharing_tag", "vip1=active")
volga629
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
