<div dir="ltr"><br><br><div class="gmail_quote">2008/9/11 CunningPike <span dir="ltr"><<a href="mailto:cunningpike@gmail.com">cunningpike@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Oliver,<br>
<br>
We use DNS SRV records combined with short TTLs</blockquote><div>How short ? <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> to provide failover.<br>
Thankfully, we have only used it when moving phones from one server to<br>
another in preparation for upgrades, but it worked like a champ then.</blockquote><div><br>I was first inclined to use DNS instead of phone feature for several reasons.<br>But I'm curious to compare those reasons with others.<br>
<br>Your experience proves using DNS makes sense :<br>it gives capability to fall back to main or backup proxy at will,<br>it doesn't hide strange phones behaviours,<br>...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
CP<br>
<div><div></div><div class="Wj3C7c"><br>
On Wed, 2008-09-10 at 15:02 +0200, Olivier wrote:<br>
> Hi,<br>
><br>
> I'm planning to deploy SIP hardphones in a serverless location.<br>
> Phones would be connected to 2 different Asterisk servers, one backing<br>
> up the other.<br>
><br>
> I would like to offer resilience and I'm wondering about the best way<br>
> to do it.<br>
><br>
> Phones themselves can register to a backup SIP proxy if first proxy<br>
> fails but, AFAIK, can't fall back to main server from backup server<br>
> when main server recovers.<br>
><br>
> I'm wondering if should use DNS, phone multi-registration feature, or<br>
> a combination of DNS and phone multi-registration feature, to<br>
> implement resilience.<br>
> Your opinion ?<br>
><br>
> Cheers<br>
><br>
</div></div>> _______________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
><br>
> AstriCon 2008 - September 22 - 25 Phoenix, Arizona<br>
> Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br>
><br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
AstriCon 2008 - September 22 - 25 Phoenix, Arizona<br>
Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br></div>