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

Pulat Ugan <p_ugan@yahoo.com> Wed, 26 December 2007 23:37 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 1J7foC-0001ia-Ny; Wed, 26 Dec 2007 18:37:08 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J7foA-0001iB-UW for sip-confirm+ok@megatron.ietf.org; Wed, 26 Dec 2007 18:37:06 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J7foA-0001i3-K9 for sip@ietf.org; Wed, 26 Dec 2007 18:37:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J7fn2-0001Oq-Rm for sip@ietf.org; Wed, 26 Dec 2007 18:35:56 -0500
Received: from web62414.mail.re1.yahoo.com ([69.147.75.91]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1J7fn2-0001GQ-Fb for sip@ietf.org; Wed, 26 Dec 2007 18:35:56 -0500
Received: (qmail 16475 invoked by uid 60001); 26 Dec 2007 23:35:51 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Dx9ouijBRYTHGuCCLmgqqzYhe9TRRBb3CnZv83nwHkPUZxYXm8BROrGag/qg6haog+8vULUlFM71k2OG9XoqAQ6lC+Eaq/S+V5fP4FEdMLjToaj+aTaGnGfZK3hi/tty81Vcx1DWnGLguQzhMBF/rqc/stDTxUE5gfpQoHVlj9g=;
X-YMail-OSG: lTQmuT0VM1n3Cx41mar.9Qpy5YHcd7I3W33BuM23eA7xK4smPD56nt6gahHFZMbWLSPyv1O_07q5w2aHbnFJFdS9yA--
Received: from [85.102.192.195] by web62414.mail.re1.yahoo.com via HTTP; Wed, 26 Dec 2007 15:35:51 PST
Date: Wed, 26 Dec 2007 15:35:51 -0800
From: Pulat Ugan <p_ugan@yahoo.com>
To: sip@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <930473.14432.qm@web62414.mail.re1.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-TMDA-Confirmed: Wed, 26 Dec 2007 18:37:06 -0500
Subject: [Sip] Processing Record Route Header in 200 OK For Further Requests
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

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=AAAAAAAEFwQNBB8EChgLATU1Mzc3NkA2My4yNTEuMjIuODI->

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