Re: [dispatch] Transfer using reINVITE
"Dale Worley" <dworley@nortel.com> Tue, 12 May 2009 15:04 UTC
Return-Path: <dworley@nortel.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFEB13A6C90 for <dispatch@core3.amsl.com>; Tue, 12 May 2009 08:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.643
X-Spam-Level:
X-Spam-Status: No, score=-6.643 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0jvTONRvUato for <dispatch@core3.amsl.com>; Tue, 12 May 2009 08:04:22 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id ED77E3A6AFC for <dispatch@ietf.org>; Tue, 12 May 2009 08:04:21 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n4CF4p828648; Tue, 12 May 2009 15:04:51 GMT
Received: from [47.141.31.149] ([47.141.31.149]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 May 2009 11:05:49 -0400
From: Dale Worley <dworley@nortel.com>
To: "Szilagyi, Mike" <Mike.Szilagyi@inin.com>
In-Reply-To: <B043FD61A001424599674F50FC89C2D71D92492DF1@ININMAIL.i3domain.inin.com>
References: <B043FD61A001424599674F50FC89C2D71D92492DF1@ININMAIL.i3domain.inin.com>
Content-Type: text/plain; charset="utf-8"
Organization: Nortel Networks
Date: Tue, 12 May 2009 11:05:48 -0400
Message-Id: <1242140748.3614.17.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 12 May 2009 15:05:49.0858 (UTC) FILETIME=[22CEB020:01C9D313]
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] Transfer using reINVITE
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2009 15:04:22 -0000
On Tue, 2009-05-12 at 10:20 -0400, Szilagyi, Mike wrote: > Is anyone familiar with a transfer scenario that uses reINVITEs? I’ve > run into a few RFPs where support for transfer using SIP re-INVITEs is > on the questionnaire. Could someone reference an RFC or draft that > describes this scenario, if there is one. In addition, many UAs, as part of executing a transfer, first put the caller on hold using re-INVITE. Though re-INVITE is not intrinsically part of the transfer, every phone that I have tested as done a re-INVITE as the first step of a transfer. Dale
- [dispatch] Transfer using reINVITE Szilagyi, Mike
- Re: [dispatch] Transfer using reINVITE Paul Kyzivat
- Re: [dispatch] Transfer using reINVITE Tan, Ya Ching (NSN - DE/Munich)
- Re: [dispatch] Transfer using reINVITE Dale Worley