Hi Amel & Wissal,
The `location` table should not be shared across multiple OpenSIPS
instances, it should be one per OpenSIPS ( similar the `dialog` or
presence related tables)
For the `dispatcher` table, the `socket` column is optional. But if you
have to use it, use the socket definition via socket tag (see [1]) - of
course, use the same socket tag in all OpenSIPS cfg instances.
[1] https://www.opensips.org/Documentation/Script-CoreParameters-3-4#socket
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 02.08.2024 11:06, [email protected] wrote:
Hello Community,
I have a question regarding the OpenSIPS database setup. I'm currently
using a Galera cluster with two OpenSIPS instances, and I'm
encountering an issue with maintaining a unified database view.
Specifically, in certain tables such as *Dispatcher* and *Location,*
the *Socket *column always contains IP addresses that are specific to
each VM. This VM-specific data prevents a unified view of the
database, causing inconsistencies between the two OpenSIPS instances.
How can I ensure that both VMs share a unified database view without
relying on VM-specific IP addresses in the Socket column?
Thank you in advance for your assistance.
On belahf of my colleague Wissal
_______________________________________________
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
