Hello list. I know that probably this questions is more related to the SIP protocol, but is causing me problems and this is a very supportive list. I'm using a HT-286 from Grandstream behind NAT. This is the REGISTER sequence : U 200.120.46.99:29786 -> 200.100.154.35:5060 REGISTER sip:myproxy.mydomain.net SIP/2.0. Via: SIP/2.0/UDP 192.168.1.100;branch=z9hG4bKafcb21cb60db91bb. From: <sip:5501234567@myproxy.mydomain.net;user=phone>;tag=478555f337ca8f10. To: <sip:5501234567@myproxy.mydomain.net;user=phone>. Contact: *. Supported: replaces, timer. Call-ID: a51e541e3b0f66fd(a)192.168.1.100. CSeq: 100 REGISTER. Expires: 0. User-Agent: Grandstream HT287 1.1.0.42 DevId 000b822197fe. Max-Forwards: 70. Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE. Content-Length: 0. . U 200.100.154.35:5060 -> 200.120.46.99:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 192.168.1.100;branch=z9hG4bKafcb21cb60db91bb;received=200.120.46.99. From: <sip:5501234567@myproxy.mydomain.net;user=phone>;tag=478555f337ca8f10. To: <sip:5501234567@myproxy.mydomain.net;user=phone>. Call-ID: a51e541e3b0f66fd(a)192.168.1.100. CSeq: 100 REGISTER. Server: Sip EXpress router (0.9.3 (i386/linux)). Content-Length: 0. Warning: 392 200.100.154.35:5060 "Noisy feedback tells: pid=29777 req_src_ip=200.120.46.99 req_src_port=29786 in_uri=sip:myproxy.mydomain.net out_uri=sip:myproxy.mydomain.net via_cnt==1". . U 200.100.154.35:5060 -> 200.120.46.99:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.100;branch=z9hG4bKafcb21cb60db91bb;received=200.120.46.99. From: <sip:5501234567@myproxy.mydomain.net;user=phone>;tag=478555f337ca8f10. To: <sip:5501234567@myproxy.mydomain.net;user=phone>;tag=6eb14299de2cc731d17 3c135064daec5.1fe9. Call-ID: a51e541e3b0f66fd(a)192.168.1.100. CSeq: 100 REGISTER. WWW-Authenticate: Digest realm="myproxy.mydomain.net", nonce="4b30e9281c52f640a2713c3011bb835d06005946", qop="auth". Server: Sip EXpress router (0.9.3 (i386/linux)). Content-Length: 0. Warning: 392 200.100.154.35:5060 "Noisy feedback tells: pid=29777 req_src_ip=200.120.46.99 req_src_port=29786 in_uri=sip:myproxy.mydomain.net out_uri=sip:myproxy.mydomain.net via_cnt==1". As you can see the initial REGISTER has a Contact header like this : Contact: *. Is this ok?. Is this ok by RFC? What does this means? In my cfg file I have : route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ----------------------------------------------------------------- sl_send_reply("100", "Trying"); if (!search("^Contact:\ +\*") && client_nat_test("7")) { setflag(6); fix_nated_register(); force_rport(); }; So I think is not matching the regexp "(!search("^Contact:\ +\*")" therefore is not fixing the contact. Any ideas? Ricardo.-