[OpenSIPS-Users] Dialog Replication in Active Active mode

Liviu Chircu liviu at opensips.org
Wed Aug 13 16:31:24 CEST 2014


Hello Jai,

Looking at your active-active configuration, I must ask:
with your model, in case OSP1 goes down, how will BYEs reach OSP2 in 
order to terminate OSP1's ongoing calls?

Your conclusions are correct. Dialog replication is designed to work 
with a common virtual IP between two OpenSIPS machines.

What looks worrying is the segfault 16 seconds after processing failed. 
In order to have that figured out,
could you please post the output of "/usr/sbin/opensips -V, along with a 
gdb backtrace? [1]

[1]: http://www.opensips.org/Documentation/TroubleShooting-Crash

Best regards,

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 08/07/2014 08:10 PM, Jai Rangi wrote:
> Hello,
>
> I am trying to setup two active active open-sip servers sharing the 
> same database. Listening on IP 192.168.1.110 (OSP1) and 192.168.1.111 
> (OSP2)
>
> This is how my dialog configuration looks like.
> OSP1
> bin_listen = 192.168.1.110:8080 <http://192.168.1.110:8080>
> bin_children = 4
> loadmodule "dialog.so"
> modparam("dialog", "hash_size", 1024)
> modparam("dialog", "default_timeout", 130)
> modparam("dialog", "db_url", 
> "mysql://dbuser:password@@192.168.1.2/opensips 
> <http://192.168.1.2/opensips>")
> modparam("dialog", "db_mode", 0)
> modparam("dialog", "db_update_period", 60)
> modparam("dialog", "profiles_with_value", "ib ; ob; io")
> modparam("dialog", "ping_interval", 20)
> modparam("dialog", "accept_replicated_dialogs", 1)
> modparam("dialog", "replicate_dialogs_to", "192.168.1.111:8080 
> <http://192.168.1.111:8080>")
>
>
> OSP2
> bin_listen = 192.168.1.111:8080 <http://192.168.1.111:8080>
> bin_children = 4
> loadmodule "dialog.so"
> modparam("dialog", "hash_size", 1024)
> modparam("dialog", "default_timeout", 130)
> modparam("dialog", "db_url", 
> "mysql://dbuser:password@@192.168.1.2/opensips 
> <http://192.168.1.2/opensips>")
> modparam("dialog", "db_mode", 0)
> modparam("dialog", "db_update_period", 60)
> modparam("dialog", "profiles_with_value", "ib ; ob; io")
> modparam("dialog", "ping_interval", 20)
> modparam("dialog", "accept_replicated_dialogs", 1)
> modparam("dialog", "replicate_dialogs_to", "192.168.1.110:8080 
> <http://192.168.1.110:8080>")
>
> When OSP1 get the call, it send the dialog packet to OSP2, OSP2 
> crashes with this message in the logs.
>
>
> Aug  7 09:45:09 localhost /usr/local/opensip/sbin/opensips[20563]: 
> WARNING:dialog:fetch_socket_info: non-local socket 
> <udp:192.168.1.110:5060 <http://192.168.1.110:5060>>...ignoring
> Aug  7 09:45:09 localhost /usr/local/opensip/sbin/opensips[20563]: 
> WARNING:dialog:fetch_socket_info: non-local socket 
> <udp:192.168.1.110:5060 <http://192.168.1.110:5060>>...ignoring
> Aug  7 09:45:09 localhost /usr/local/opensip/sbin/opensips[20563]: 
> ERROR:dialog:dlg_replicated_create: Dialog in DB doesn't match any 
> listening sockets
> Aug  7 09:45:09 localhost /usr/local/opensip/sbin/opensips[20563]: 
> ERROR:dialog:dlg_replicated_create: Received malformed UDP binary packet!
> Aug  7 09:45:09 localhost /usr/local/opensip/sbin/opensips[20563]: 
> ERROR:dialog:receive_binary_packet: Failed to process a binary packet!
> Aug  7 09:45:23 localhost /usr/local/opensip/sbin/opensips[20559]: 
> INFO:core:handle_sigs: child process 20562 exited by a signal 11
> Aug  7 09:45:23 localhost /usr/local/opensip/sbin/opensips[20559]: 
> INFO:core:handle_sigs: core was generated
> Aug  7 09:45:23 localhost /usr/local/opensip/sbin/opensips[20559]: 
> INFO:core:handle_sigs: terminating due to SIGCHLD
> Aug  7 09:45:23 localhost /usr/local/opensip/sbin/opensips[20561]: 
> INFO:core:sig_usr: signal 15 received
> Aug  7 09:45:23 localhost /usr/local/opensip/sbin/opensips[20570]: 
> INFO:core:sig_usr: signal 15 received
>
>
> I found two threads with no solutions and from the threads it looks 
> like dialog replication wont work in active active configuration. It 
> required a shared IP and will work for failover only.
> I will appreciate any suggestions, or if some can share working 
> configuration.
>
> Thank you,
> -Jai
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140813/64e7784f/attachment.htm>


More information about the Users mailing list