RE: [Sip] Providing Delayed Call Information

"James M. Polk" <jmpolk@cisco.com> Thu, 26 January 2006 18:18 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2Bhi-0002jB-0p; Thu, 26 Jan 2006 13:18:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2Bhf-0002i6-C1 for sip@megatron.ietf.org; Thu, 26 Jan 2006 13:18:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11865 for <sip@ietf.org>; Thu, 26 Jan 2006 13:17:08 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F2Brd-0000B1-Oi for sip@ietf.org; Thu, 26 Jan 2006 13:28:59 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 26 Jan 2006 10:18:26 -0800
X-IronPort-AV: i="4.01,221,1136188800"; d="scan'208"; a="396854043:sNHT32271680"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k0QIIPWH005150; Thu, 26 Jan 2006 10:18:26 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 26 Jan 2006 10:18:26 -0800
Received: from jmpolk-wxp.cisco.com ([10.21.145.124]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 26 Jan 2006 10:18:25 -0800
Message-Id: <4.3.2.7.2.20060126121511.03e125d8@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 26 Jan 2006 12:18:24 -0600
To: Brett Tate <brett@broadsoft.com>, 'David Benoit' <benoit@infointeractive.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Sip] Providing Delayed Call Information
In-Reply-To: <000601c622a0$b88a2210$2c28a8c0@brett1>
References: <20060126170707.GF20718@infointeractive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-OriginalArrivalTime: 26 Jan 2006 18:18:25.0649 (UTC) FILETIME=[E610F610:01C622A4]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sip@ietf.org
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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

At 12:48 PM 1/26/2006 -0500, Brett Tate wrote:
> > It's a B2BUA.  In terms of using a re-INVITE, I want to
> > present the updated information _before_ the call is
> > answered, so that's a no go. That's also why I had initially
> > looked into using the UPDATE method, but, sadly, that doesn't
> > seem to be able to affect anything but the media parameters.
> >
> > Any chance UPDATE could be updated to do so?
>
>UPDATE can basically update everything that a re-INVITE can.

But that list is the

Call-ID
To
 From (and tag)
CSeq

and this "problem" seems to want to modify the From (and From tag) fields, 
which makes UPDATE and reINVITE each a non-starter.

>However if I
>recall correctly, some on the sip list view the concepts of updating
>identities and retargeting as evil.
>
>The topic was discussed within the following thread.
>
>http://130.230.52.14/list-archive/sip/msg07664.html
>
>
>
>
>_______________________________________________
>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

_______________________________________________
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