<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Just to mention that ucarp can be a very basic alternative to
corosync/pacemaker to manage the virtual ip. A simple app, but
usually keeps working...</p>
<p>Cheers,<br>
Daniel<br>
</p>
<br>
<div class="moz-cite-prefix">On 06/06/16 02:21, Fred Posner wrote:<br>
</div>
<blockquote
cite="mid:C880ACAA-E856-4FD8-B28C-5165504CF25C@palner.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div>If it's just 2 servers, consider as Juha said,
corosync/pacemaker with drbd. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature"><span style="background-color:
rgba(255, 255, 255, 0);">Fred Posner</span>
<div><span style="background-color: rgba(255, 255, 255, 0);">direct:
+1 (224) 334-FRED (3733)</span></div>
</div>
<div><br>
On Jun 5, 2016, at 5:26 PM, Moacir Ferreira <<a
moz-do-not-send="true"
href="mailto:moacirferreira@hotmail.com"><a class="moz-txt-link-abbreviated" href="mailto:moacirferreira@hotmail.com">moacirferreira@hotmail.com</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Hi,<br>
<br>
Sorry... I should have mentioned before. You guys are
thinking on the standard Internet SIP calls' behavior while
I am trying to use Kamailio on a large "industrial" project.
This said:<br>
<br>
Assuming that the end-point is "smart", the DNS method is
functional but it would take quite a while before the UA
(phone) recovers from the previous name/IP binding it has in
cache;<br>
SRV is good for a "smart" UA that, unfortunately, is not the
case;<br>
Same for the phone units as they are industrial "Help
Points" and so quite "dummy".<br>
<br>
While I never tested it, I thought I could use two Kamailio
servers with a mysql cluster like mariadb-galera where, for
Kamailio functions, one server would be "active" and another
"passive" server. Then use keepalived for monitoring the
"active" Kamailio and starting the "passive" server if the
active Kamailio fails. Without any testing, tests that I
think I should have done before putting questions in here,
my questions are:<br>
<br>
Suppose that I have two Kamailio servers, one "active" and
another one "passive" (not running) where the mysql
databases are synchronized in between two servers using
MySQL Galera. Using keepalived I would monitor the active
Kamailio instance. Should it fails, start the "passive"
Kamailio instance using the same MySQL database that were
supposed to be synchronized. Would this new Kamailio
instance be able to find a called number? Why this question?
As long as I understand, Kamailio will always challenge the
UA for authentication before making a call, so if this
second server gets a call request it would just challenge
and authenticate the caller. The "key point" would be having
this new Kamailio instance aware about the called
destinations. So, delivering a MySQL database, with the
latest data the active Kamailio had, to this new Kamailio
instance would be enough to allow it find the called party?<br>
<br>
Anyway, can you guys comment on my "thoughts"? Is it
possible? Am I missing something? Would you suggest another
approach for such scenario?<br>
<br>
Cheers!<br>
Moacir <br>
<br>
<div>
<hr id="stopSpelling">Date: Sun, 5 Jun 2016 21:07:41 +0200<br>
From: <a moz-do-not-send="true"
href="mailto:chabert.loic.74@gmail.com">chabert.loic.74@gmail.com</a><br>
To: <a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
Subject: Re: [SR-Users] High availability<br>
<br>
<p dir="ltr">Hello Bill,</p>
<p dir="ltr">I have made kamailio ha using exabgp with
loopbacks.</p>
<p dir="ltr">Check <a moz-do-not-send="true"
href="https://github.com/Exa-Networks/exabgp"
target="_blank">https://github.com/Exa-Networks/exabgp</a></p>
<p dir="ltr">With bgp, kamailio cluster can be splited on
severals datacenters.</p>
<p dir="ltr">Regards.</p>
<div class="ecxgmail_quote">Le 5 juin 2016 20:53, "Bill"
<<a moz-do-not-send="true"
href="mailto:bill@novatrope.us">bill@novatrope.us</a>>
a écrit :<br>
<blockquote class="ecxgmail_quote"
style="border-left:1px #ccc solid;padding-left:1ex;">
<div> Hi Moacir<br>
<br>
We have only found three ways to handle failover.<br>
1. Change the DNS entry whenever a failure is
detected.<br>
2. Use SRV records to display an alternate route.<br>
3. Use the failover mechanism in the phone itself<br>
<br>
1. works, but it may take some time for your ua's to
become aware of the change<br>
2. never have been able to get this to work as
advertised.<br>
3. Works pretty well depending on the phone. (We use
mostly Yealink's and they seem to handle the
failover pretty well.)<br>
<br>
Hope this helps<br>
<br>
<div>On 06/05/2016 07:41 AM, Moacir Ferreira wrote:<br>
</div>
<blockquote>
<div dir="ltr">Hi,<br>
<br>
I got two questions regarding high availability:<br>
<br>
1 - Should my Kamailio server fail, I would like
another Kamailio "box/server" to take over with
minimum services disruption. What is the
"community" advice for such environment?<br>
<br>
2 - Should my main PSTN gateway fail, what would
be the best mechanism to redirect calls to a
second PSTN gateway?<br>
<br>
Cheers!<br>
Moacir<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a></div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a> - <a class="moz-txt-link-freetext" href="http://www.kamailio.org">http://www.kamailio.org</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</body>
</html>