<br><br><div class="gmail_quote">On Wed, Feb 29, 2012 at 10:43 AM, Carlos Alvarez <span dir="ltr"><<a href="mailto:carlos@televolve.com">carlos@televolve.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Wed, Feb 29, 2012 at 8:41 AM, Steve Totaro<br>
<<a href="mailto:stotaro@asteriskhelpdesk.com">stotaro@asteriskhelpdesk.com</a>> wrote:<br>
> Agreed with one exception, the endpoint behind the NAT DOES need to be setup<br>
> correctly to keep the router from seeing inbound traffic to the device as<br>
> unsolicited and drop it. That is a function of the router but keep alives<br>
> from Qualify on the Asterisk side, and setting the device to register every<br>
> few minutes will keep that mapping open and alive, letting traffic pass as<br>
> solicited.<br>
<br>
</div>We use qualify=yes on Asterisk and a few months ago turned OFF the<br>
keep-alive feature on all SIP clients on our entire system. This is<br>
working fine, and we did it because of a strange bug/behavior with<br>
certain versions of Cisco SPA series firmware.<br>
<div class="im HOEnZb"><br>
<br>
--<br>
Carlos Alvarez<br>
TelEvolve<br>
<a href="tel:602-889-3003" value="+16028893003">602-889-3003</a><br>
<br>
</div><div class="HOEnZb"><div class="h5"></div></div></blockquote><div><br></div><div>So you turned it off on the phones but use it on the Asterisk side?</div><div><br></div><div>Do you set a value or just use qualify=yes?</div>
<div><br></div><div>I had many problems with qualify over VSAT as ping times and jitter are crazy. 700ms ping times were considered "Good" from the IZ in Iraq to Equinix data center in VA, it took some tweaking to find the right value so a phone that was "Reachable" was not labeled "Unreachable", I did want phones that were truly unreachable to be marked as such, more to spot patterns and act on them or with the vendor.</div>
<div><br></div><div>Did you submit a bug report? If it is easy to reproduce and you feel like helping out, report it. I do not report issues if there is a simple way to do the same thing, but I know I should.</div><div>
<br></div><div>What does the debug or strange behavior look like? Probably a variance in the RFC implementation.<br></div><div><br></div><div>Thanks,</div><div>Steve T</div></div>