<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hello,</div><div><br></div><div>We're looking to add a second Opensips instance on a separate server for failover. Or, from an operational perspective, it could be described as "active-active" since both will be available at any one time. We'll control the traffic flow to the proxies with the SRV records used by the clients.</div><div><br></div><div>Looking through the db tables used, it seems there may be some conflict with the location and dialog tables.</div><div><br></div><div>The usrloc module clearly saves the local socket used during the registration. Is there a way to tell Opensips 1.6 to ignore this when loading the record? That way, either proxy can use records saved by either proxy. A force socket option perhaps to the local IP? Clients are all public IPs – no NAT.</div><div><br></div><div>The dialog table also saves the local sockets. Will there be a conflict here? I don't expect the Opensips processes to use each other's dialogs, so my goal is they will simply ignore each others' records.</div><div><br></div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><div><br></div></body></html>