RE: [Sip] Processing Record Route Header in 200 OK For Further Requests

"Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com> Thu, 27 December 2007 00:08 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J7gIS-0008TG-EQ; Wed, 26 Dec 2007 19:08:24 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J7gIR-0008T9-Bo for sip-confirm+ok@megatron.ietf.org; Wed, 26 Dec 2007 19:08:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J7gIR-0008T1-0G for sip@ietf.org; Wed, 26 Dec 2007 19:08:23 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J7gIQ-0001tQ-Hy for sip@ietf.org; Wed, 26 Dec 2007 19:08:22 -0500
X-IronPort-AV: E=Sophos;i="4.24,209,1196636400"; d="scan'208";a="1749076"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 27 Dec 2007 01:08:15 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBR08FjW020299; Thu, 27 Dec 2007 01:08:15 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lBR08FgE017961; Thu, 27 Dec 2007 00:08:15 GMT
Received: from xbh-rtp-201.amer.cisco.com ([64.102.31.12]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Dec 2007 01:08:15 +0100
Received: from xmb-rtp-215.amer.cisco.com ([64.102.31.124]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Dec 2007 19:08:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Processing Record Route Header in 200 OK For Further Requests
Date: Wed, 26 Dec 2007 19:08:13 -0500
Message-ID: <8983EC086A9D954BA74D9763E853CF3E0467C546@xmb-rtp-215.amer.cisco.com>
In-Reply-To: <930473.14432.qm@web62414.mail.re1.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Processing Record Route Header in 200 OK For Further Requests
thread-index: AchIGEt6u4J3bc1PTPmRQ/IFb+yu2gABAK/w
From: "Sanjay Sinha (sanjsinh)" <sanjsinh@cisco.com>
To: Pulat Ugan <p_ugan@yahoo.com>, sip@ietf.org
X-OriginalArrivalTime: 27 Dec 2007 00:08:13.0942 (UTC) FILETIME=[92CF9160:01C8481C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1850; t=1198714095; x=1199578095; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sanjsinh@cisco.com; z=From:=20=22Sanjay=20Sinha=20(sanjsinh)=22=20<sanjsinh@cisc o.com> |Subject:=20RE=3A=20[Sip]=20Processing=20Record=20Route=20H eader=20in=20200=20OK=20For=20Further=20Requests |Sender:=20; bh=pO/KejvLvCcGoihN8D0aL2vXSD9Em1a21QvQFdsekhQ=; b=LeJKsZMviGzoGYGhdxEl5gO96y7669d6rOepx+1qhPZVD8V5IBKqCCHWDQ uCPseNT1TDLiLWj8QqIjpGudsk3+zhbhDlsBbRYovL6aO/g4gv3ifIj80vSN 2hrCeheMqk;
Authentication-Results: ams-dkim-1; header.From=sanjsinh@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc:
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Since the proxy supports loose routing, for subsequent requests on the
dialog, the request-uri should be the Contact header uri and
Record-Route header value should be put in Route header.

Sanjay

>-----Original Message-----
>From: Pulat Ugan [mailto:p_ugan@yahoo.com] 
>Sent: Wednesday, December 26, 2007 6:36 PM
>To: sip@ietf.org
>Subject: [Sip] Processing Record Route Header in 200 OK For 
>Further Requests
>
>Hi,
>
>When a UA gets record-route header and contact header in 200 
>OK. like below
>------------------------------------------------
>contact:sip:{fqdn}:5060
>Record-Route:<sip:{ip};lr=on;ftag=100428709;vsf=AAAAAAAEFwQNBB8
>EChgLATU1Mzc3NkA2My4yNTEuMjIuODI->
>
>What should be the uri in the re-invite message to put UAS on 
>hold.. And if we use the record-route header as uri, 
>should/may we put the contact header in 200 OK as route header?
>
>And the issue I am having for the end of above scenario; 
>should uri of ACK message be contact header coming from UAS in 
>200 OK regardless of whatever record-route or contact header  
>we previously got in initial call setup.?
>
>I will really appreciate if anyone can suggest any 
>reference-document which is including sample flows about 
>processing record-route headers on UAC side.
>
>Thanks..
>
>
>
>      
>_______________________________________________________________
>_____________________
>Never miss a thing.  Make Yahoo your home page. 
>http://www.yahoo.com/r/hs
>
>
>
>_______________________________________________
>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol Use 
>sip-implementors@cs.columbia.edu for questions on current sip 
>Use sipping@ietf.org for new developments on the application of sip
>


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip