You may want to consider something like UCARP with a cold standby. Of course you can use the REAL IP of the backup for a warm standby.<div><br></div><div><br></div><div>if both instances of opensips are using the SAME IP, it'll cause problems.. There are better ways.</div>
<div>-Brett</div><div><br><br><div class="gmail_quote">On Mon, Sep 21, 2009 at 3:00 PM, Noel R. Morais <span dir="ltr"><<a href="mailto:noelrocha@gmail.com">noelrocha@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Stanisław,<br>
<br>
It's for redundancy. I'm using a network configuration where both<br>
server send requests using the same ip address (a virtual ip address).<br>
<br>
Balancing using SRV records is reliable? What happen if on of my<br>
servers goes down? Can I trust that the client side will take the<br>
other record for sending requests?<br>
<br>
Thanks,<br>
<br>
Noel<br>
<br>
2009/9/21 Stanisław Pitucha <<a href="mailto:viraptor@gmail.com">viraptor@gmail.com</a>>:<br>
<div><div></div><div class="h5">> 2009/9/21 Noel R. Morais <<a href="mailto:noelrocha@gmail.com">noelrocha@gmail.com</a>>:<br>
>> I'm using the kernel IPVS and keepalived for healthcheck.<br>
>><br>
>> I couldn't find a way to make sure that the ACK will go to the same<br>
>> server that generated the INVITE. :(<br>
>><br>
>> Thanks for your help Brett, I will keep looking for some solution.<br>
><br>
> A general question for a start - why do you want to load-balance the<br>
> traffic? Are you hitting the limit of what one host can do, or is it<br>
> for redundancy?<br>
><br>
> If it's for redundancy... don't ;) Setting up 2 opensips servers with<br>
> a simple ip failover gives you a lot less headache than any external<br>
> load-balanced solution. (many phones are not clever enough and they<br>
> have problem with receiving packets coming from *the other* server)<br>
> If it's because you *really* cannot handle all the traffic on one<br>
> host, then look at balancing on the client side via SRV records. In my<br>
> experience you'll get a distribution like 33/66 % between two servers.<br>
> Maybe that will be enough for you?<br>
><br>
> --<br>
> KTHXBYE,<br>
><br>
> Stanisław Pitucha, Gradwell Voip Engineer<br>
><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>
<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>
</div></div></blockquote></div><br></div>