Re: [Sip] [Sip-implementors] Different SDP Session Version in 183 &200 OK

"Jaiswal, Sanjiv (NSN - IN/Bangalore)" <sanjiv.jaiswal@nsn.com> Wed, 09 March 2011 10:29 UTC

Return-Path: <sanjiv.jaiswal@nsn.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D27463A68DE for <sip@core3.amsl.com>; Wed, 9 Mar 2011 02:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level:
X-Spam-Status: No, score=-4.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_13=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+gisc+zgimc for <sip@core3.amsl.com>; Wed, 9 Mar 2011 02:29:20 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id CC9533A6846 for <sip@ietf.org>; Wed, 9 Mar 2011 02:29:19 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p29AUTTj028734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Mar 2011 11:30:29 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p29AUSHB012884; Wed, 9 Mar 2011 11:30:29 +0100
Received: from SGSIEXC007.nsn-intra.net ([10.159.224.87]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Mar 2011 11:30:28 +0100
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
Date: Wed, 09 Mar 2011 18:30:23 +0800
Message-ID: <FAA28CD01112C94CA8BBE2EFA6CBB2313489AE@SGSIEXC007.nsn-intra.net>
In-Reply-To: <AANLkTik5eKMvETfbFZQiZDW=ZbQ=CHwbFh+D1S4dTXd-@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip-implementors] [Sip] Different SDP Session Version in 183 &200 OK
Thread-Index: AcvePSf1VoxZIuPSSzmM0f9sMbLp+QABog+g
References: <AANLkTimQfN_1sMhtxjgQOoTWTz_wHJf86Nyu7_L17MkS@mail.gmail.com><AANLkTinfNaFy3F0BAf8Pe00hiNTFMFsBApxZzNOUW1nK@mail.gmail.com><E13C8C03049AFA4E9CEE5A21D3E7F85DB51531B3@GUREXMB02.ASIAN.AD.ARICENT.COM> <AANLkTik5eKMvETfbFZQiZDW=ZbQ=CHwbFh+D1S4dTXd-@mail.gmail.com>
From: "Jaiswal, Sanjiv (NSN - IN/Bangalore)" <sanjiv.jaiswal@nsn.com>
To: ext Nitin Kapoor <nitinkapoorr@gmail.com>, Ashish Saxena <ashish2.saxena@aricent.com>
X-OriginalArrivalTime: 09 Mar 2011 10:30:28.0536 (UTC) FILETIME=[02728380:01CBDE45]
X-Mailman-Approved-At: Fri, 11 Mar 2011 01:24:03 -0800
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] [Sip-implementors] Different SDP Session Version in 183 &200 OK
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2011 10:31:52 -0000

Hi Nitin,


Every SDP with incremented session ( in this case 200 OK) is treated as
new negotiation(offer).
Whether ACK from other end contains SDP answer? If yes then session
version is incremented there also?


Regards
Sanjiv

-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of ext
Nitin Kapoor
Sent: Wednesday, March 09, 2011 3:03 PM
To: Ashish Saxena
Cc: sip@ietf.org; sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] [Sip] Different SDP Session Version in
183 &200 OK

Hello Ashish,

Here is the mline for both the messages.

183:

Media Description, name and address (m): audio 43888 RTP/AVP 18

200 OK:

Media Description, name and address (m): audio 43888 RTP/AVP 18

Thanks,
Nitin Kapoor


On Wed, Mar 9, 2011 at 3:25 AM, Ashish Saxena
<ashish2.saxena@aricent.com>wrote:

> what is the mline of 200OK SDP.
>
> Regards
> Ashish Saxena
> (www.aricent.com)
> ________________________________________
> From: sip-bounces@ietf.org [sip-bounces@ietf.org] On Behalf Of Nitin
> Kapoor [nitinkapoorr@gmail.com]
> Sent: Wednesday, March 09, 2011 12:54 PM
> To: sip-implementors@lists.cs.columbia.edu
> Cc: sip@ietf.org
> Subject: Re: [Sip] Different SDP Session Version in 183 & 200 OK
>
> Hello All,
>
> Could any one please help me out on requested query as below.
>
> Thanks,
> Nitin
>
> On Tue, Mar 8, 2011 at 4:48 PM, Nitin Kapoor <nitinkapoorr@gmail.com
> <mailto:nitinkapoorr@gmail.com>> wrote:
> Dear All,
>
> I have one call scenario where my termination is sending the SDP in
183 as
> well as in 200 OK also. As far as i know if we are getting SDP in 183
> session progress then my UAC can ignore the SDP in 200 OK. Also most
of the
> time SDP is same.
>
> But here i noticed the slight difference of "Session Version". Here
when my
> termination is sending 188 Session Progress with SDP is sending the
SDP as
> below.
>
> I can see that  my Termination is incrementing  "Session Version" for
SDP
> in 183 & 200 OK in same dialog..
>
> 183 with SDP
>
> S_OWNER : o=TLPMSXP2 22660 22660 IN IP4 69.90.230.210
> S_NAME : s=sip call
> S_CONNECT : c=IN IP4 69.90.230.217
> TIME : t=0 0
> M_NAME : m=audio 59072 RTP/AVP 18 4 8 98
>
> 200 OK with SDP:
>
> S_OWNER : o=TLPMSXP2 22660 22661 IN IP4 69.90.230.210
> S_NAME : s=sip call
> S_CONNECT : c=IN IP4 69.90.230.217
> TIME : t=0 0
>
> Could anyone please let me know if that is okay to increment the
session
> version and if any supported document is there?
>
> Thanks,
> Nitin
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended
solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or
used
> for any purpose other than for what it is intended. If you have
received
> this message in error, please notify the originator immediately. If
you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents
of this
> message. Aricent accepts no responsibility for loss or damage arising
from
> the use of the information transmitted by this email including damage
from
> virus."
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors