[Sip] regarding session modification

Srinivas <srinivasj@huawei.com> Wed, 16 January 2008 13:31 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 1JF8Mc-0005HX-7t; Wed, 16 Jan 2008 08:31:30 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JF8MZ-0004pv-W5 for sip-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 08:31:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JF8MZ-0004jI-F4 for sip@ietf.org; Wed, 16 Jan 2008 08:31:27 -0500
Received: from szxga04-in.huawei.com ([61.144.161.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF8MP-0005Qq-OK for sip@ietf.org; Wed, 16 Jan 2008 08:31:27 -0500
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JUQ00BLCO6SQ4@szxga04-in.huawei.com> for sip@ietf.org; Wed, 16 Jan 2008 21:30:28 +0800 (CST)
Received: from huawei.com ([172.24.1.18]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JUQ00BK3O6OO3@szxga04-in.huawei.com> for sip@ietf.org; Wed, 16 Jan 2008 21:30:27 +0800 (CST)
Received: from htipl60927 ([10.18.3.113]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JUQ004MJO6M6C@szxml03-in.huawei.com> for sip@ietf.org; Wed, 16 Jan 2008 21:30:24 +0800 (CST)
Date: Wed, 16 Jan 2008 19:00:22 +0530
From: Srinivas <srinivasj@huawei.com>
To: sip@ietf.org
Message-id: <00fb01c85843$f2be9ad0$7103120a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: AchYQ/CtSaa2AGwwSomJEjhRwgkSQg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b54c114e377ffd3b8a24b9a620caaf11
Subject: [Sip] regarding session modification
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="===============1827363563=="
Errors-To: sip-bounces@ietf.org

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