Closed #306.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/306#event-155986444___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Hi Liviu,
I think your argumentation is right, we will think about using one dialog table
per instance so that we never encounter this issue.
Regards,
Mickael
---
Reply to this email directly or view it on GitHub:
Hello Mickael,
Is this a real-life scenario? To me, this looks like a problem which should not
be addressed, since there are alternatives (either deploy a backup instance for
each primary instance, or put more load on one machine, and make the other one
a backup). You can use dialog
Hi Liviu,
This is the architecture we use for a long time.
We have N OpenSIPS instances that share the same dialog table. Traffic is load
balanced over the instances. I agree that dialogs are exclusive to each
instance (a dialog that doesn't belong to an instance would be ignored by this
Hi,
After the dialog table schema has been changed to replace the hash_entry and
hash_id columns by the new dlg_id column, the dlg_id column is now the primary
key of the table (while only an index - non UNIQUE - was defined before for the
(hash_entry,hash_id) columns).
With a configuration
