[dispatch] Transfer using reINVITE
"Szilagyi, Mike" <Mike.Szilagyi@inin.com> Tue, 12 May 2009 14:18 UTC
Return-Path: <Mike.Szilagyi@inin.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 EEB7A3A6DA7 for <dispatch@core3.amsl.com>; Tue, 12 May 2009 07:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level:
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[AWL=-0.730, BAYES_20=-0.74, HTML_MESSAGE=0.001]
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 pY6H54DYbBDq for <dispatch@core3.amsl.com>; Tue, 12 May 2009 07:18:56 -0700 (PDT)
Received: from inin.com (smtpgw.inin.com [209.43.1.24]) by core3.amsl.com (Postfix) with ESMTP id B35223A6D07 for <dispatch@ietf.org>; Tue, 12 May 2009 07:18:56 -0700 (PDT)
Received: from ININHUB1 [172.16.1.156] by smtpgw.inin.com - Websense Email Security (6.1.1); Tue, 12 May 2009 10:20:27 -0400
Received: from ININMAIL.i3domain.inin.com ([172.16.1.186]) by ininhub1.i3domain.inin.com ([172.16.1.156]) with mapi; Tue, 12 May 2009 10:20:27 -0400
From: "Szilagyi, Mike" <Mike.Szilagyi@inin.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Date: Tue, 12 May 2009 10:20:25 -0400
Thread-Topic: Transfer using reINVITE
Thread-Index: AcnTDMs1eQ0iV9OVQeOW5yVQDnpN4g==
Message-ID: <B043FD61A001424599674F50FC89C2D71D92492DF1@ININMAIL.i3domain.inin.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_B043FD61A001424599674F50FC89C2D71D92492DF1ININMAILi3dom_"
MIME-Version: 1.0
X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1
X-SEF-ZeroHour-RefID: fgs=4
X-SEF-Processed: 6_1_1_105__2009_05_12_10_20_27
Subject: [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 14:18:58 -0000
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. Regards, Mike
- [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