Yep - this was already checked. I've not changed by ser.cfg file in weeks. I'm using nat_flag=6 in the registrar module.<br>
<br>
I'm not using flag 6 for anything other than NAT, and if client_nat_test("7") is true then I call setflag(6).<br>
<br>
Here is the exact section of my ser.cfg. I therefore feel that the last
"cvs up" I did against rel_0_9_0 somehow caused the issue.<br>
<br>
if (!search("^Contact:\ +\*") && client_nat_test("7")) {<br>
setflag(6);
# inform registrar module of NATed client<br>
fix_nated_register();<br>
force_rport();<br>
};<br>
<br>Here is what it seems like. It seems that when a truly NATed client
registers, the flag column is set properly, but subsequent non-NATed
clients get flagged as being NATed because some variable isn't being
reset properly either in the registrar or usrloc modules.<br>
<br>
The reason I say this is because when I restart ser, with zero records
in the location table, the first registration works fine. The flag is 1
for NATed clients and 0 or non-NATed clients, but over time all the
flags eventually get set to 1 for all records. So it's almost like some
variable is not being properly initialized.<br>
<br>
Regards,<br>
Paul<br><div><span class="gmail_quote">On 6/10/05, <b class="gmail_sendername">Jan Janak</b> <<a href="mailto:jan@iptel.org">jan@iptel.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10-06-2005 11:09, Java Rockx wrote:<br>> Hi All.<br>><br>> Here's a bit more info on the usrloc "flags" bug.<br>><br>> This register message was flagged at NATed eventhough my "nat_flag" was not
<br>> set.<br>><br>> U 2005/06/10 11:01:27.853890 <a href="http://71.9.17.51:5060">71.9.17.51:5060</a> <<a href="http://71.9.17.51:5060">http://71.9.17.51:5060</a>> -><br>> <a href="http://10.3.0.221:5060">
10.3.0.221:5060</a> <<a href="http://10.3.0.221:5060">http://10.3.0.221:5060</a>><br>> REGISTER sip:<a href="http://sipdev.mycompany.net">sipdev.mycompany.net</a> <<a href="http://sipdev.mycompany.net">http://sipdev.mycompany.net
</a>> SIP/2.0.<br>> Via: SIP/2.0/UDP <a href="http://71.9.17.51:5060">71.9.17.51:5060</a> <<a href="http://71.9.17.51:5060">http://71.9.17.51:5060</a>><br>> ;branch=z9hG4bK1106535059.<br>> From: Paul <
<a href="mailto:sip:3215590000@sipdev.company.net">sip:3215590000@sipdev.company.net</a>>;tag=3843647257.<br>> To: Paul <<a href="mailto:sip:3215590000@sipdev.company.net">sip:3215590000@sipdev.company.net</a>>.
<br>> Call-ID: <a href="mailto:1846387046@71.9.17.51">1846387046@71.9.17.51</a>.<br>> CSeq: 778 REGISTER.<br>> Contact: <sip:3215590000@71.9.17.51:5060>.<br>> Authorization: Digest username="3215590000",
<br>> realm="<a href="http://sipdev.mycompany.net">sipdev.mycompany.net</a><<a href="http://sipdev.mycompany.net">http://sipdev.mycompany.net</a>>",<br>> nonce="42a9ac7341e18f72830c3cd553fecfbd0c9fc6", uri="sip:
<br>> <a href="http://sipdev.company.net:5060">sipdev.company.net:5060</a> <<a href="http://sipdev.company.net:5060">http://sipdev.company.net:5060</a>>",<br>> response="5443dedef7bfa7fb4a033af66a2392c", algorithm=MD5,
<br>> cnonce="3dc4445e42acd47873ca563a9942104a", qop=auth, nc=00000193.<br>> max-forwards: 70.<br>> expires: 900.<br>> Content-Length: 0.<br>><br>><br>> Another thing I see is that all usrloc records end up having the flag column
<br>> set to 1 wheather the client is NATed or not. I'm setting the registrar<br>> modules nat_flag using client_nat_test("7") when processing REGISTER<br>> messages, however usrloc is not correctly setting the NAT_FLAG.
<br><br> The default value of nat_flag parameter in registrar module is 4. Make<br> sure you set that flag if client_nat_test returns true and that you<br> are not using that flag for anything else.<br><br> Jan.<br>
<br></blockquote></div><br>