Hi Chen-Che,
I would suggest using a shared IP between PA and PB (via vrrp or
heartbeat), so when traffic moves from PA to PB, the IP will also move,
so the dialogs from DB will be consistent with the IP of the server.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/30/2013 11:20 AM, microx wrote:
Hi all,
After changing the listening port of pgpool to 5432 (default postgresql
port), the dlg_db_sync() function indeed tries
to load dialog info from DB. However, because PA and PB are both active (for
load balancing) with different IP
addresses, the dlg_db_sync() does not allow the loading of dialogs
associated with PA from DB to the PB's memory.
The error message is like "dialog in DB does not match any listening
sockets".
It seems that dlg_db_sync() is not workable for my scenario. Can someone
help me address this issue? Many thanks
in advance.
Sincerely,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Failover-and-dialog-termination-tp7584192p7584285.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
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
