RE: [Sip] Providing Delayed Call Information
"Brett Tate" <brett@broadsoft.com> Thu, 26 January 2006 17:48 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 1F2BEK-0004oH-7F; Thu, 26 Jan 2006 12:48:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F2BEH-0004n3-Fd for sip@megatron.ietf.org; Thu, 26 Jan 2006 12:48:17 -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 MAA08977 for <sip@ietf.org>; Thu, 26 Jan 2006 12:46:43 -0500 (EST)
Received: from bdsoft10.vwh.net ([130.94.149.229]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F2BOG-0007MK-5S for sip@ietf.org; Thu, 26 Jan 2006 12:58:37 -0500
Received: from brett1 (corp.broadsoft.com [67.88.7.2]) (authenticated bits=0) by bdsoft10.vwh.net (8.13.1/8.12.11) with ESMTP id k0QHldGs092652; Thu, 26 Jan 2006 12:47:43 -0500 (EST)
From: Brett Tate <brett@broadsoft.com>
To: 'David Benoit' <benoit@infointeractive.com>
Subject: RE: [Sip] Providing Delayed Call Information
Date: Thu, 26 Jan 2006 12:48:25 -0500
Message-ID: <000601c622a0$b88a2210$2c28a8c0@brett1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <20060126170707.GF20718@infointeractive.com>
X-PMX-IsInternal: True
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
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
> 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. 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] Providing Delayed Call Information David Benoit
- Re: [Sip] Providing Delayed Call Information David Benoit
- Re: [Sip] Providing Delayed Call Information David Benoit
- Re: [Sip] Providing Delayed Call Information Cullen Jennings
- RE: [Sip] Providing Delayed Call Information Brett Tate
- RE: [Sip] Providing Delayed Call Information James M. Polk
- RE: [Sip] Providing Delayed Call Information Brett Tate
- RE: [Sip] Providing Delayed Call Information Michael Hammer (mhammer)
- RE: [Sip] Providing Delayed Call Information James M. Polk
- RE: [Sip] Providing Delayed Call Information Kasturi Narayanan