RE: [Sip] regarding session modification

<kamalakar.mergu@wipro.com> Wed, 16 January 2008 13:36 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 1JF8RN-0001wj-Rh; Wed, 16 Jan 2008 08:36:25 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JF8RM-0001wI-RJ for sip-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 08:36:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF8RM-0001vy-Gd for sip@ietf.org; Wed, 16 Jan 2008 08:36:24 -0500
Received: from wip-cdc-wd.wipro.com ([203.91.201.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF8RJ-0005a6-1g for sip@ietf.org; Wed, 16 Jan 2008 08:36:24 -0500
Received: from wip-cdc-wd.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id EA49018067 for <sip@ietf.org>; Wed, 16 Jan 2008 19:06:16 +0530 (IST)
Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92]) by wip-cdc-wd.wipro.com (Postfix) with ESMTP id D4EEF18053 for <sip@ietf.org>; Wed, 16 Jan 2008 19:06:16 +0530 (IST)
Received: from HYD-MDP-MBX01.wipro.com ([10.150.50.182]) by blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 16 Jan 2008 19:06:19 +0530
Received: from HYD-MKD-MBX01.wipro.com ([10.154.50.181]) by HYD-MDP-MBX01.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 16 Jan 2008 19:06:18 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Sip] regarding session modification
Date: Wed, 16 Jan 2008 19:05:18 +0530
Message-ID: <24BCDE728664A5429097057C063C9D64027659E9@HYD-MKD-MBX01.wipro.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] regarding session modification
Thread-Index: AchYQ/CtSaa2AGwwSomJEjhRwgkSQgAALHr4
References: <00fb01c85843$f2be9ad0$7103120a@china.huawei.com>
From: kamalakar.mergu@wipro.com
To: srinivasj@huawei.com, sip@ietf.org
X-OriginalArrivalTime: 16 Jan 2008 13:36:18.0511 (UTC) FILETIME=[C620ADF0:01C85844]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: f9c0d585568a86447c98453afdf94aa0
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>
Content-Type: multipart/mixed; boundary="===============0189643560=="
Errors-To: sip-bounces@ietf.org

What is the header field that is changed in all re-INVITEs.
What is the value of this header field in each scenario?

________________________________

From: Srinivas [mailto:srinivasj@huawei.com]
Sent: Wed 1/16/2008 7:00 PM
To: sip@ietf.org
Subject: [Sip] regarding session modification



Hi all,

Consider the following scenarios. 

 

1. 

C->S: INVITE (for speechrecog)

S->C: 200 OK

C->S: ACK

 

Now the SIP session is established b/w UAC and UAS. speechrecog resource is active on the established sip session

 

C->S: INVITE (re-INVITE for adding speechsynth resource)

S->C: 200 OK 

Offer/Answer fail for the new resource, TTS (speechsynth).

 

 

2. 

C->S: INVITE (for speechrecog)

S->C: 200 OK

C->S: ACK

 

Now the SIP session is established b/w UAC and UAS. speechrecog resource is active on the established sip session.

 

C->S: INVITE (re-INVITE for adding speechsynth resource)

S->C: 200 OK 

Offer/Answer fail for the for the existing ASR(speechrecog) resource also.

 

3.

C->S: INVITE (for speechrecog)

S->C: 200 OK

C->S: ACK

 

Now the SIP session is established b/w UAC and UAS. speechrecog resource is active

 

C->S: INVITE (re-INVITE for adding speechsynth resource)

S->C: 200 OK

C->S: ACK

 

Now both speechrecog and speechsynth are active on the sip session

 

C->S: INVITE (re-INVITE for removing speechsynth resource)

S->C: 486 BUSY HERE

 

 

What should be the behaviour of UAC in the above scenarios?

 

 

Regds,

Srinivas

 

 

_______________________________________________
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