On Thu, Jan 31, 2013 at 9:26 AM, Adam Moffett <span dir="ltr"><<a href="mailto:adamlists@plexicomm.net" target="_blank">adamlists@plexicomm.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br></div>
Maybe it's possible to send a NOTIFY to a peer on the last IP it was seen at? I don't think I've seen anything that has a "register" command, but lots of devices can get a "check your config" or "reboot" command via SIP NOTIFY.<br>
</blockquote><div><br></div><div>If you can notify, you can call. This fixes nothing other than refreshing NAT if that's involved.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
....I'm more wondering why the peer is unregistered but we still expect to communicate with it. Other than a network problem or the device being unplugged...neither of which could be fixed from the server.</blockquote>
<div><br></div><div>I have a feeling that some people in this discussion have a lack of understanding about the SIP protocol and the underlying networking that could affect it. The original post failed to say whether this was on a LAN without routing, on a LAN with routing, or a WAN. Each of those could result in totally different results and solutions.</div>
<div><br></div></div><div><br></div>-- <br><div>Carlos Alvarez</div><div>TelEvolve</div><div>602-889-3003</div><div><br></div>