RE: [SIP] 3PCC and the re-invite response

Igor Slepchin <ISlepchin@dynamicsoft.com> Fri, 01 December 2000 21:56 UTC

Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA01493 for <sip-archive@odin.ietf.org>; Fri, 1 Dec 2000 16:56:03 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id A485144406; Fri, 1 Dec 2000 15:56:09 -0500 (EST)
Delivered-To: sip@lists.bell-labs.com
Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51]) by lists.bell-labs.com (Postfix) with ESMTP id 01012443D7 for <sip@lists.bell-labs.com>; Fri, 1 Dec 2000 15:55:25 -0500 (EST)
Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50]) by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id QAA20257; Fri, 1 Dec 2000 16:57:45 -0500 (EST)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21) id <X2075MZ4>; Fri, 1 Dec 2000 16:53:17 -0500
Message-ID: <B65B4F8437968F488A01A940B21982BF3CE98B@DYN-EXCH-001.dynamicsoft.com>
From: Igor Slepchin <ISlepchin@dynamicsoft.com>
To: 'Brett Tate' <brett@broadsoft.com>, Igor Slepchin <ISlepchin@dynamicsoft.com>, Sip Mail List <sip@lists.bell-labs.com>
Subject: RE: [SIP] 3PCC and the re-invite response
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Sender: sip-admin@lists.bell-labs.com
Errors-To: sip-admin@lists.bell-labs.com
X-BeenThere: sip@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:sip-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:sip@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/sip>, <mailto:sip-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/sip/
Date: Fri, 01 Dec 2000 16:53:12 -0500

> -----Original Message-----
> From: Brett Tate [mailto:brett@broadsoft.com]
> 
> My post was to solve the SDP exchange loop
> problem of using 3pcc to pull the subscribers
> off of hold.
> 
> Otherwise, the flow in the following post works.
> http://lists.bell-labs.com/pipermail/sip/2000q4/004391.html
> 

What I'm saying is that I don't see this as a problem with 3pcc at all.
Given Figure 1 in
http://search.ietf.org/internet-drafts/draft-rosenberg-sip-3pcc-01.txt, why
would A change the media in 200OK to the second INVITE? Instead of inventing
workarounds for eccentric UAs, it would be much easier to define what a
"sane" UA can and cannot do (e.g., it cannot change SDP just because it
received a re-INVITE, there should be another valid reason for the change).

---
Igor Slepchin


_______________________________________________
SIP mailing list
SIP@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/sip