<div dir="ltr">Here is the error, I see it checking the ip address against the listening ip address, and of course it does not match, if I add the other ip address as a listening address opensips wont start.<div><br></div><div><br></div><div><br><div><div>Feb 18 17:17:10 sipsvr6 /sbin/opensips[26864]: ERROR:usrloc:receive_ucontact_update: non-local socket <udp:<a href="http://45.45.99.95:5060">45.45.99.95:5060</a>></div><div>Feb 18 17:17:10 sipsvr6 /sbin/opensips[26864]: ERROR:usrloc:receive_ucontact_update: failed to process replication event. dom: 'location', aor: '<a href="mailto:solhome5@sipsvr5.myserver.com">solhome5@sipsvr5.myserver.com</a>'</div><div>Feb 18 17:17:10 sipsvr6 /sbin/opensips[26864]: ERROR:usrloc:receive_binary_packet: failed to process a binary packet!</div></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 18, 2015 at 5:02 PM, Liviu Chircu <span dir="ltr"><<a href="mailto:liviu@opensips.org" target="_blank">liviu@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div><tt>Hello Schneur,<br>
<br>
1) If REGISTER request replication properly works (same messages
received on both sides), then the backup should not delete
contacts like you are mentioning.<br>
2) Yes, it will. You can disable this behaviour with
"skip_replicated_db_ops" [1]<br>
3) Any specific ERRORs in the logfile? Please open a GitHub
ticket for any obvious issues [2]<br>
4) Only integrity checking. But that can be bypassed by a
potential attacker. Immediate solutions are the use of private
interfaces and/or iptables rules.<br>
5) Yes, replication is only to be used with floating IPs.
Regarding the distributed redundant setup, a big discussion was
started in 2013, yet did not really come to a final conclusion
[3]<br>
<br>
[1]:
<a href="http://www.opensips.org/html/docs/modules/2.1.x/usrloc.html#skip_replicated_db_ops" target="_blank">http://www.opensips.org/html/docs/modules/2.1.x/usrloc.html#skip_replicated_db_ops</a><br>
[2]: <a href="https://github.com/OpenSIPS/opensips/issues" target="_blank">https://github.com/OpenSIPS/opensips/issues</a><br>
[3]: <a href="http://opensips.org/pipermail/users/2013-April/025204.html" target="_blank">http://opensips.org/pipermail/users/2013-April/025204.html</a><br>
<br>
Best regards,<br>
</tt>
<pre cols="72">Liviu Chircu
OpenSIPS Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre><div><div class="h5">
On 18.02.2015 12:19, Schneur Rosenberg wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div class="h5">
<div dir="ltr">I have a question regarding binary replication, I
was using OpenSIPS 1.7 until now, my backup was passive, because
when they were all up at the same time, the usrloc timer from
the backup kept on removing users from the database, even though
I'm using mode 2, I still rely on the DB for some actions, I
recently watched <span style="color:rgb(0,0,0)">Vlad Paiu video
presentation on Binary Interface replication and he says that
he advises to leave the backup open too, so I built 2 test
servers with OpenSIPS 1.11 and I have a few questions.</span>
<div><span style="color:rgb(0,0,0)"><br>
</span></div>
<div><span style="color:rgb(0,0,0)">1) will this solve the issue
of the usrloc timer deleting records?</span></div>
<div><font color="#000000">2) will it also update the backups
database if I use mode 2? this way I dont need to replicate
the db's, i will have 2 separate db's and have each server
update its own db, if it does this will also solve problem
1.</font></div>
<div><font color="#000000">3) I tested the bin replication, when
doing a ngrep I see the packet coming in on the backup when
a new user registers, but when doing a "opensipsctl ul show"
it only shows the contact line and nothing else and it
disappears </font><span style="color:rgb(0,0,0)">completely</span><span style="color:rgb(0,0,0)"> </span><span style="color:rgb(0,0,0)"> after a few moments and it does
not update the db.</span></div>
<div><font color="#000000">4) Does it have a built in
security mechanism besides manually doing it with iptables?</font></div>
<div><font color="#000000">5) It seems like this is mainly used
with a floating ip, I have servers on the same network using
floating ip, I also have servers on different networks using
failover dns, how will it affect my redundancy, I assume the
backup server wont be able to reach the client before the
client does a new DNS lookup and re registers, because the
clients NAT wont allow it through, is that correct? and is
there a solution for that?</font></div>
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000">thanks in advance</font></div>
<div><font color="#000000">S. Rosenberg </font></div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>