Re: [BLISS] Comments on draft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)

"Hutton, Andrew" <andrew.hutton@siemens-enterprise.com> Mon, 27 April 2009 14:37 UTC

Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 955593A68FD for <bliss@core3.amsl.com>; Mon, 27 Apr 2009 07:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 mf4UuAynPUXO for <bliss@core3.amsl.com>; Mon, 27 Apr 2009 07:37:19 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id AED933A6971 for <bliss@ietf.org>; Mon, 27 Apr 2009 07:37:19 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KIR0009QKM714@siemenscomms.co.uk> for bliss@ietf.org; Mon, 27 Apr 2009 15:37:19 +0100 (BST)
Date: Mon, 27 Apr 2009 15:36:58 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
In-reply-to: <a2ef85430904242329p1baf3fa4o7e366d9a3f7a928c@mail.gmail.com>
To: Michael Procter <michael@voip.co.uk>, Francois Audet <audet@nortel.com>
Message-id: <719F9BBB3E7E71428A2D13F3D76C768F01A1EF33@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable
Thread-Topic: [BLISS] Comments on draft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
Thread-Index: AcnFb0O6YHABvGWyQKm6mcct82A4ngB1VQnw
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <F592E36A5C943E4E91F25880D05AD1140937CB3E@zrc2hxm0.corp.nortel.com> <a2ef85430904240846k3a301efk4302165a3d9eded1@mail.gmail.com> <1ECE0EB50388174790F9694F77522CCF1DA436E8@zrc2hxm0.corp.nortel.com> <a2ef85430904242329p1baf3fa4o7e366d9a3f7a928c@mail.gmail.com>
Cc: bliss@ietf.org, Scott Orton <orton@nortel.com>
Subject: Re: [BLISS] Comments on draft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2009 14:37:20 -0000

Hi,

I think the auto-retrieve timer is really something that would be
implemented in the park server and the phone does not need to know
anything about it.

What might be useful from the parking UA's perspective is that when the
call is auto-retrieved (i.e. the park server refer's the call back to
the parking UA or possibly a different UA) that the resulting INVITE
contains an indication that the INVITE is a result of the auto-retrieve
initiated by the park server. Could we say something about this in the
draft?

Regards
Andy

 

>-----Original Message-----
>From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] 
>On Behalf Of Michael Procter
>Sent: 25 April 2009 07:30
>To: Francois Audet
>Cc: bliss@ietf.org; Scott Orton
>Subject: Re: [BLISS] Comments on 
>draft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
>
>2009/4/24 Francois Audet <audet@nortel.com>:
>> On the firest part, you are correct, it's not new protocol.
>>
>> But a default timer, and a paragraph on Auto-Retrieve is
>> exactly the type of information that is appropriate for
>> an INFORMATIONAL draft.
>>
>> Introducing phones that don't have an Auto-retrieve feature
>> for call park will cause significant headaches in the real world.
>
>What, exactly, does a phone have to do to have an 'Auto-retrieve'
>feature?  As far as I can tell, all the service policy you have
>described so far is for the park server, not the phone.
>
>Michael
>_______________________________________________
>BLISS mailing list
>BLISS@ietf.org
>https://www.ietf.org/mailman/listinfo/bliss
>