RE: [Sipping] Question on ReInvite procedures

"Bert Culpepper" <bert.culpepper@intervoice-brite.com> Wed, 22 August 2001 21:24 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24347 for <sipping-archive@odin.ietf.org>; Wed, 22 Aug 2001 17:24:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02112; Wed, 22 Aug 2001 17:15:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02026 for <sipping@ns.ietf.org>; Wed, 22 Aug 2001 17:15:34 -0400 (EDT)
Received: from mail2.intervoice-brite.com (mail2.intervoice-brite.com [204.62.8.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24155 for <sipping@ietf.org>; Wed, 22 Aug 2001 17:14:12 -0400 (EDT)
Received: from 172.16.16.64 (gwsmtpsrv.intervoice.com [172.16.16.64]) by mail2.intervoice-brite.com (Build 101 8.9.3/NT-8.9.3) with SMTP id QAA05608 for <sipping@ietf.org>; Wed, 22 Aug 2001 16:20:05 -0500
Received: from bculpepperpc ([151.214.151.122]) by 172.16.16.64; Wed, 22 Aug 2001 16:14:40 -0500
From: Bert Culpepper <bert.culpepper@intervoice-brite.com>
To: 'Hemant Agrawal' <hagrawal@telverse.com>, sipping@ietf.org
Subject: RE: [Sipping] Question on ReInvite procedures
Date: Wed, 22 Aug 2001 17:14:31 -0400
Message-ID: <000401c12b4f$704a1ac0$7a97d697@orlando.brite.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <F96BD6D84E58C849A82C7309061785170D4FF1@dc1.telverse.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

This kind of behavior is discussed in draft-rosenberg-sip-3pcc-01.txt.
It STRONGLY RECOMMENDs that UAs do not change their address and port
assignments in responses to re-INVITEs when asked to change the address
and port they send media to.  However, if the SDP in the re-INVITE
changes the codec for a media stream, then the re-INVITE response can
contain a different address and port from that of the initial request.

This behavior on the part of UAs is required for 3rd-party call control
in SIP.  But is not required in RFC2543.  RFC2543bis touches on this in
appendix B but for a little different scenario.  That is, re-INVITE w/o
SDP, 200 with "previous SDP" (offer), and ACK with SDP (answer).  In the
first paragraph of section B.4 it states "... the offerer SHOULD offer
the same SDP it provided previously if it has no reason to change
anything."  It's up to implementers to comply with the recommendation
above for 3pcc to work.

To answer your questions given the above, A should not change any media
encoding aspects for a stream if it doesn't want B to change its
address/port.  If B wants to change its port, it should complete the
re-INVITE from A then issue its own re-INVITE.

regards,
Bert

> -----Original Message-----
> From: sipping-admin@ietf.org
> [mailto:sipping-admin@ietf.org]On Behalf Of
> Hemant Agrawal
> Sent: Wednesday, August 22, 2001 3:45 PM
> To: sipping@ietf.org
> Subject: [Sipping] Question on ReInvite procedures
>
>
>  Hi all,
>          I have a question on ReINVITE procedures.
>    1.  Party A sends a INVITE to Party B with SDP as IP = a
> and port = b
>        It gets a 200 OK from Party B with SDP as IP = m and port = n
>
>    2. Party A sends a ReINVITE to Party B with SDP as IP = c
> and port =
> d
>       It gets a 200 OK from Party B with SDP as IP = m and port = o
>
>    My questions here are:
>    i. Is this behavior proper? What should be done, if Party
> A does not
> want Party B to change its SDP port or keep the same connection?
>
>    ii.) If this is not a proper behavior,  the Party B should respond
> with same SDP as previous with IP = m and port = n.  Than
> What should be
> done, if Party B wants Party B to change its SDP port or open new
> connection?
>
>
>   Waiting for your response!
>
> Thanks
> Hemant
>
>
>
>
>
> _______________________________________________
> Sipping mailing list  http://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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