<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<blockquote
cite="mid:CAJLBXEn5izpj1V7S4wJ1Ng5ng8+Aoh89xa7vBC2zToZjD9S3mA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="im">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>This is the answer. If 100% availability
is critical, your IP addresses shouldn't be
changing anyway, so take the registration
process out entirely. </div>
</div>
<br>
</div>
</div>
</blockquote>
</div>
This advice is not valid for android / iphones though.<br>
</div>
</blockquote>
<div><br>
</div>
<div style="">That's absurd. Why would you use a
battery-powered smartphone if you are trying to have 100%
availability?</div>
<br>
</div>
</div>
</div>
</blockquote>
From what i understood from the original post, Xbrian is looking for
a way to work around broken phones that fail to register when they
should. I doubt his idea of 100% availability is the same as yours
or he would/should be using a different brand/model of phones.<br>
+ The mobile phone will survive a power outage, because of the
register you could be behind NAT as it will open the bindings, you
can take it to the bathroom etc.<br>
<br>
I'm just trying to illustrate the possible advantages of a register
before XBbrian redoes his network config.<br>
<br>
Z<br>
<br>
<br>
<br>
<br>
</body>
</html>