Hi BogDan,

Yes, I see Record-Route  header in the 200 ok.......
Please can u check the  ngrepped  of the X-lite
with Hard phones iit is fine ...........
Below one  is ngrep from X-lite users,

           U 192.168.2.3:5060 -> 61.17.248.68:2645
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 192.168.2.19:5060;received=61.17.248.68;rport=2645;branch=z9hG4bK07D6ABA60AB44ED785D560E08E4FB906.
From: 9004 <sip:9004@59.93.61.80>;tag=2300839400.
To: <sip:9005@59.93.61.80>;tag=1115807967.
Contact: <sip:9005@61.17.248.68:5060>.
Record-Route: <sip:192.168.2.3:5060;nat=yes;ftag=2300839400;lr=on>.
Call-ID: 79F5551B-74DF-46D6-99B0-81D1B0B62DE2@192.168.2.19.
CSeq: 28497 INVITE.
Server: X-Lite release 1103m.
Content-Length: 0.
#
U 61.17.248.68:5060 -> 192.168.2.3:5060
#
U 61.17.248.68:2645 -> 192.168.2.3:5060
#
U 61.17.248.68:5060 -> 192.168.2.3:5060
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.2.3;branch=z9hG4bK82f3.04882de2.0;received=59.93.61.80.
Via: SIP/2.0/UDP 192.168.2.19:5060;received=61.17.248.68;rport=2645;branch=z9hG4bK07D6ABA60AB44ED785D560E08E4FB906.
From: 9004 <sip:9004@59.93.61.80>;tag=2300839400.
To: <sip:9005@59.93.61.80>;tag=1115807967.
Contact: <sip:9005@192.168.2.3:5060>.
Record-Route: <sip:192.168.2.3:5060;nat=yes;ftag=2300839400;lr=on>.
Call-ID: 79F5551B-74DF-46D6-99B0-81D1B0B62DE2@192.168.2.19.
CSeq: 28497 INVITE.
Content-Type: application/sdp.
Server: X-Lite release 1103m.
Content-Length: 290.
v=0.
o=9005 8334687 8344000 IN IP4 192.168.2.3.
s=X-Lite.
c=IN IP4 192.168.2.3.
t=0 0.
m=audio 16358 RTP/AVP 0 8 3 98 97 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:8 pcma/8000.
a=rtpmap:3 gsm/8000.
a=rtpmap:98 iLBC/8000.
a=rtpmap:97 speex/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
#
U 192.168.2.3:5060 -> 61.17.248.68:2645
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.2.19:5060;received=61.17.248.68;rport=2645;branch=z9hG4bK07D6ABA60AB44ED785D560E08E4FB906.
From: 9004 <sip:9004@59.93.61.80>;tag=2300839400.
To: <sip:9005@59.93.61.80>;tag=1115807967.
Contact: <sip:9005@61.17.248.68:5060>.
Record-Route: <sip:192.168.2.3:5060;nat=yes;ftag=2300839400;lr=on>.
Call-ID: 79F5551B-74DF-46D6-99B0-81D1B0B62DE2@192.168.2.19.
CSeq: 28497 INVITE.
Content-Type: application/sdp.
Server: X-Lite release 1103m.
Content-Length: 290.
.
v=0.
o=9005 8334687 8344000 IN IP4 192.168.2.3.
s=X-Lite.
c=IN IP4 192.168.2.3.
t=0 0.
m=audio 16358 RTP/AVP 0 8 3 98 97 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:8 pcma/8000.
a=rtpmap:3 gsm/8000.
a=rtpmap:98 iLBC/8000.
a=rtpmap:97 speex/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
--------------No ACK  reuest to sip server -----------

And the Below  one is ngrep from Cisco ATA 188 phone

#
U 192.168.2.3:5060 -> 61.17.248.68:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 192.168.2.4:5060;rport=5060;received=61.17.248.68;branch=z9hG4bKf83dc9b8da84bb0d.
Record-Route: <sip:192.168.2.3:5060;nat=yes;ftag=944392830;lr=on>.
From: 9001 <sip:9001@59.93.61.80;user=phone>;tag=944392830.
To: <sip:9002@59.93.61.80;user=phone>;tag=606700996.
Call-ID: 1749181330@192.168.2.4.
CSeq: 2 INVITE.
Require: 100rel.
RSeq: 1.
Contact: 9002 <sip:9002@61.17.248.68:5060;user=phone;transport=udp>.
Server: Cisco ATA 188  v3.2.1 atasip (050616A).
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE.
Content-Length: 0.
#
#
U 61.17.248.68:5060 -> 192.168.2.3:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.2.3;branch=z9hG4bKa7ef.3290d1b6.0.
Via: SIP/2.0/UDP 192.168.2.4:5060;rport=5060;received=61.17.248.68;branch=z9hG4bKf83dc9b8da84bb0d.
Record-Route: <sip:192.168.2.3:5060;nat=yes;ftag=944392830;lr=on>.
From: 9001 <sip:9001@59.93.61.80;user=phone>;tag=944392830.
To: <sip:9002@59.93.61.80;user=phone>;tag=606700996.
Call-ID: 1749181330@192.168.2.4.
CSeq: 2 INVITE.
Contact: 9002 <sip:9002@192.168.2.4:5060;user=phone;transport=udp>.
Server: Cisco ATA 188  v3.2.1 atasip (050616A).
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE.
Supported: replaces.
Content-Length: 193.
Content-Type: application/sdp.
.
v=0.
o=9002 13872 13872 IN IP4 192.168.2.4.
s=ATA186 Call.
c=IN IP4 192.168.2.4.
t=0 0.
m=audio 16384 RTP/AVP 0 101.
a=rtpmap:0 PCMU/8000/1.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.

#
U 192.168.2.3:5060 -> 61.17.248.68:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.2.4:5060;rport=5060;received=61.17.248.68;branch=z9hG4bKf83dc9b8da84bb0d.
Record-Route: <sip:192.168.2.3:5060;nat=yes;ftag=944392830;lr=on>.
From: 9001 <sip:9001@59.93.61.80;user=phone>;tag=944392830.
To: <sip:9002@59.93.61.80;user=phone>;tag=606700996.
Call-ID: 1749181330@192.168.2.4.
CSeq: 2 INVITE.
Contact: 9002 <sip:9002@61.17.248.68:5060;user=phone;transport=udp>.
Server: Cisco ATA 188  v3.2.1 atasip (050616A).
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE.
Supported: replaces.
Content-Length: 193.
Content-Type: application/sdp.
.
v=0.
o=9002 13872 13872 IN IP4 192.168.2.4.
s=ATA186 Call.
c=IN IP4 192.168.2.4.
t=0 0.
m=audio 16384 RTP/AVP 0 101.
a=rtpmap:0 PCMU/8000/1.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
U 61.17.248.68:5060 -> 192.168.2.3:5060
ACK sip:9002@61.17.248.68 SIP/2.0.
Route: <sip:192.168.2.3:5060;nat=yes;ftag=944392830;lr=on>.
Via: SIP/2.0/UDP 192.168.2.4:5060;branch=z9hG4bKdcc7a733706e39e7.
From: 9001 <sip:9001@59.93.61.80;user=phone>;tag=944392830.
To: <sip:9002@59.93.61.80;user=phone>;tag=606700996.
Call-ID: 1749181330@192.168.2.4.
CSeq: 2 ACK.
User-Agent: Cisco ATA 188  v3.2.1 atasip (050616A).
Proxy-Authorization: Digest username="9001",realm="59.93.61.80",nonce="45c31da4f01c51af5f0ae0ea1e59af3cc6bb49eb",uri="sip:9002@59.93.61.80 ",response="89fb53d2e67d31adfee6dee63ea75108",qop=auth,nc=00000003,cnonce="28491128".
Content-Length: 0.
.

#
U 192.168.2.3:5060 -> 61.17.248.68:5060
ACK sip:9002@61.17.248.68 SIP/2.0.
Max-Forwards: 10.
Record-Route: <sip:192.168.2.3;lr=on;ftag=944392830>.
Via: SIP/2.0/UDP 192.168.2.3;branch=z9hG4bKa7ef.3290d1b6.2.
Via: SIP/2.0/UDP 192.168.2.4:5060;received=61.17.248.68;branch=z9hG4bKdcc7a733706e39e7.
From: 9001 <sip:9001@59.93.61.80;user=phone>;tag=944392830.
To: <sip:9002@59.93.61.80;user=phone>;tag=606700996.
Call-ID: 1749181330@192.168.2.4.
CSeq: 2 ACK.
User-Agent: Cisco ATA 188  v3.2.1 atasip (050616A).
Proxy-Authorization: Digest username="9001",realm="59.93.61.80",nonce="45c31da4f01c51af5f0ae0ea1e59af3cc6bb49eb",uri="sip:9002@59.93.61.80 ",response="89fb53d2e67d31adfee6dee63ea75108",qop=auth,nc=00000003,cnonce="28491128".
Content-Length: 0.



On 2/5/07, Bogdan-Andrei Iancu <bogdan@voice-system.ro> wrote:
Ravi,

so you see any Record-Route hdrs in the 200 OK reply?

regards,
bogdan

raviprakash sunkara wrote:

> Hi BogDan,
> Good AfterNoon, and Thanks For replying to me,
>
>             I  used the Following code for  Record_route();
>
>               route {
>                                    ....
>                                .....
>                               if(method=="INVITE" && nat_uac_test("3") )
>                              {
>                                     record_route_preset("sip:
> 192.168.2.3:5060 <http://192.168.2.3:5060>;nat=yes");
>                              }else if ( method  ! = " REGISTER ")
>                           {
>                                  record_route();
>                           }
>                         }
> where 192.168.2.3:5060 <http://192.168.2.3:5060> is the  private IP of
> the SIP server   behind the NAT.
>
>
> On 2/5/07, * Bogdan-Andrei Iancu* <bogdan@voice-system.ro
> <mailto:bogdan@voice-system.ro>> wrote:
>
>     Hi Ravi,
>
>     do you do record_route() for the INVITE? if not, the sequential
>     requests
>     of the dialog will bypass your server.
>
>     regards,
>     bogdan
>
>     raviprakash sunkara wrote:
>
>     > Hello Users,
>     >
>     > When  I tested the OpenSER server  with  CISCO ATA 186/188 IP phones
>     > SIP EyeP media (Softphnoes )  is working fine with RTP ,  when Both
>     > Users and SIP  Server  is in Behind the NAT,
>     >
>     > But Problem with Softphones ( X-lite ) .
>     >
>     > When I ngrep the Calls of X-lite users i didn't see any Ack
>     Packet to
>     > OpenSER  After the   Invite Packets received .
>     >
>     > Please Help me  in this Part
>     >
>     >
>     > --
>     > Thanks and Regards
>     > Ravi Prakash Sunkara
>     > ravi.sunkara@hyperion-tech.com
>     <mailto:ravi.sunkara@hyperion-tech.com>
>     <mailto:ravi.sunkara@hyperion-tech.com
>     <mailto:ravi.sunkara@hyperion-tech.com>>
>     > M:+91 9985077535
>     > O:+91 40 23114549
>     > F:+91 40 40208727
>     > ravi.sunkara@hyperion-tech.com
>     <mailto:ravi.sunkara@hyperion-tech.com> <mailto:
>     ravi.sunkara@hyperion-tech.com
>     <mailto:ravi.sunkara@hyperion-tech.com>>
>     > www.hyperion-tech.com <http://www.hyperion-tech.com>
>     <http://www.hyperion-tech.com>
>     >
>     >------------------------------------------------------------------------
>
>     >
>     >_______________________________________________
>     >Users mailing list
>     >Users@openser.org <mailto: Users@openser.org>
>     > http://openser.org/cgi-bin/mailman/listinfo/users
>     >
>     >
>
>
>
>
> --
> Thanks and Regards
> Ravi Prakash Sunkara
> ravi.sunkara@hyperion-tech.com <mailto:ravi.sunkara@hyperion-tech.com >
> M:+91 9985077535
> O:+91 40 23114549
> F:+91 40 40208727
> ravi.sunkara@hyperion-tech.com <mailto: ravi.sunkara@hyperion-tech.com>
> www.hyperion-tech.com <http://www.hyperion-tech.com>





--
Thanks and Regards
Ravi Prakash Sunkara
ravi.sunkara@hyperion-tech.com
M:+91 9985077535
O:+91 40 23114549
F:+91 40 40208727
ravi.sunkara@hyperion-tech.com
www.hyperion-tech.com