[OpenSIPS-Users] Failover and dialog termination

Bogdan-Andrei Iancu bogdan at opensips.org
Fri Feb 1 13:04:58 CET 2013

Hi Chen-Che,

Even if you do that, it would not completely solve your problem - with 
your hack, you will be able to make opensipsB to recognize the dialogs 
created on opensipsA, but the problem is calls from opensipsA are 
RecordRouted with the IP of A, so all sequestional requests for those 
calls will be sent to IP A (from the other call legs). So to make it 
work, you need to move the IP A to opensipsB, in order to receive the 
traffic related to calls on opensipsA.

Use 2 floating IPs (one on A, one on B) and in case of failure, move the 
faulty one on the other machine.


Bogdan-Andrei Iancu
OpenSIPS Founder and Developer

On 01/31/2013 05:10 AM, microx wrote:
> Hi Bogdan-Andrei,
> Thanks for your suggestion. However, I require two active proxy servers for
> better performance.
> The present solution is to add an additional column to the dialog table and
> update the caller_sock
> &  callee_sock before running dlg_db_sync(). The impact of such a behavior on
> performance remains
> to be investigated. Any better solution is very welcome. Thanks.
> Best wishes,
> Chen-Che
> --
> View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Failover-and-dialog-termination-tp7584192p7584302.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

More information about the Users mailing list