<p>Bogdan, the answer is yes to your first question.</p>
<p>I also tested whether check_ip_address() is returning 0 by adding open/close braces for each of the if/return 0 statements and placing a comment before the return statement and the comments do not print nor does function perform the final return -1 at the end. It silently dies there on some requests from the same dialog for that client in the example. </p>
<p>The loop in the ClientNatTest() indeed is stopped, because the check_ip_address() is hung/stopped. This may be a compiler/platform feature. </p>
<p>Some data for that:</p>
<p>INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:ClientNatTest: NAT test=1 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:rfc1918address: NAT NETADDR=16241<br>
INFO:nat_traversal:ClientNatTest: NAT test=2 src=xxx.xxx.xxx.xxx:8039<br>
INFO:nat_traversal:test_source_address: NAT different_ip=-1 via1_port=44043 different_port=1<br>
INFO:nat_traversal:ClientNatTest: NAT success= 2</p>
<p>Indicates the client is trying until eventually test is successful, but client still not logged in. </p>
<p>In other tests such as a simple "whois" from the command line on the IP, it has an unusual delay before returning results. </p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/issues/401#issuecomment-72469767">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AFOciS-FWVe3zmxBdboC_rJtVlELsSOBks5nn4ckgaJpZM4DOPEM.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
<link itemprop="url" href="https://github.com/OpenSIPS/opensips/issues/401#issuecomment-72469767"></link>
<meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>