IETF Logo Mail Archive

Re: [dispatch] Transfer using reINVITE

Paul Kyzivat <pkyzivat@cisco.com> Tue, 12 May 2009 14:41 UTC

Return-Path: <pkyzivat@cisco.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 CDDD528C115 for <dispatch@core3.amsl.com>; Tue, 12 May 2009 07:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.185
X-Spam-Level:
X-Spam-Status: No, score=-6.185 tagged_above=-999 required=5 tests=[AWL=0.414, 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 WdTlaC6Q8H2W for <dispatch@core3.amsl.com>; Tue, 12 May 2009 07:41:39 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id D057328C101 for <dispatch@ietf.org>; Tue, 12 May 2009 07:41:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,182,1241395200"; d="scan'208";a="44003648"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 12 May 2009 14:43:09 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n4CEh9WO019163; Tue, 12 May 2009 10:43:09 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n4CEh9DQ025695; Tue, 12 May 2009 14:43:09 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 May 2009 10:43:08 -0400
Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 May 2009 10:43:08 -0400
Message-ID: <4A098AFD.20001@cisco.com>
Date: Tue, 12 May 2009 10:43:09 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Szilagyi, Mike" <Mike.Szilagyi@inin.com>
References: <B043FD61A001424599674F50FC89C2D71D92492DF1@ININMAIL.i3domain.inin.com>
In-Reply-To: <B043FD61A001424599674F50FC89C2D71D92492DF1@ININMAIL.i3domain.inin.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 12 May 2009 14:43:08.0294 (UTC) FILETIME=[F7408260:01C9D30F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=784; t=1242139389; x=1243003389; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[dispatch]=20Transfer=20using=20reINVIT E |Sender:=20 |To:=20=22Szilagyi,=20Mike=22=20<Mike.Szilagyi@inin.com>; bh=lcXO0tOOCbBYu2kboUsk85qi3P61J8mmreYTzL7O7xc=; b=fOHRsry5gkXUwCJFLwB8kSwfqUtEltz8guW4EgRJVFPu2iO4nIn60QeYOu fXUfglOPsSKbfB1f0nqgHlW/dsv0w0zA/r759ajOi9TIAIPRz2uDY/wpr2Fk egvI6N+xLC;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
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 14:41:39 -0000

Transfer can only be accomplished using reinvite if there is an 
intermediary in the call path. I think you must be talking about 3pcc. 
There is an RFC on that but I don't have the number at hand.

	Thanks,
	Paul

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.
> 
>  
> 
> Regards,
> 
> Mike
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email