<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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 class="moz-cite-prefix">On 06/05/2016 07:41 AM, Moacir Ferreira
wrote:<br>
</div>
<blockquote cite="mid:COL131-W203818622E49EF2DF387DCC85B0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<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 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>
</body>
</html>