<p>Hi,</p>
<p>Thats very simple.</p>
<p>Use sip realtime registration with mysql and heartbit to control switiching.</p>
<p>Regards,</p>
<p>Carlos M Cruz</p>
<p><blockquote type="cite">Em 2011/02/08 16:07, "Vieri" <<a href="mailto:rentorbuy@yahoo.com">rentorbuy@yahoo.com</a>> escreveu:<br><br>Hi,<br>
<br>
Suppose you have 2 identical Asterisk servers and 1 alias IP address that you assign to either one, according to system failures, etc.<br>
Also suppose that all SIP clients register requests go to the alias IP address.<br>
<br>
Imagine server1 fails and server2 gets the alias IP address. Correct me if I'm wrong but I would have to wait at least 60 seconds before most SIP clients re-register to server2 and that server2 knows that they are actually "on-line" so calls can be routed to them.<br>
<br>
How can I minimize this time lapse? Can Asterisk "notify" all SIP clients in its sip.conf that they need to acknowledge being on-line or not (thus forcing re-registration in my scenario)?<br>
<br>
Thanks,<br>
<br>
Vieri<br>
<br>
<br>
<br>
<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>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</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></p>