Re: [Sip] willis-sip-answeralert-00

Dean Willis <dean.willis@softarmor.com> Wed, 31 August 2005 05:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAKmO-0006qz-LB; Wed, 31 Aug 2005 01:04:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAKmJ-0006oC-JR for sip@megatron.ietf.org; Wed, 31 Aug 2005 01:04:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02085 for <sip@ietf.org>; Wed, 31 Aug 2005 01:04:50 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAKnz-0000xk-04 for sip@ietf.org; Wed, 31 Aug 2005 01:06:36 -0400
Received: from [192.168.2.103] (sj-natpool-220.cisco.com [128.107.248.220]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j7V590Gu025037 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 31 Aug 2005 00:09:01 -0500
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0385938D@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF0385938D@zrc2hxm0.corp.nortel.com>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <b1d8174456b3b89dbf9e8440782b0cd6@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] willis-sip-answeralert-00
Date: Wed, 31 Aug 2005 00:04:38 -0500
To: Francois Audet <audet@nortel.com>
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: IETF SIP List <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

On Jul 29, 2005, at 2:58 PM, Francois Audet wrote:

> This answeralert stuff is quite useful.
>
> The document talks about it's applicability to Push-to-talk.
>
> I would also like to see a mention of it's usefulness for other
> features.
>
> In particular, you can use it for Intercom call features (like on
> any traditional PBX).
>

That makes sense to me, and I've added this into the revised draft.

> Also, it would be extremely useful to allow the answer-mode to be
> allowed in an UPDATE (and re-INVITE). That would enable many features
> that are available today on traditional PBXs (secretary override, and
> other fun stuff difficult to do today).
>

I started adding this in, and realized I didn't understand the usage in 
UPDATE (or, probably, re-INVITE). Since there is no new dialog being 
requested, and consequently no "answering", what good does it do to 
discuss answering modes?

So clearly your hinting at a usage that I haven't quite grokked yet. 
Please elaborate.

--
Dean


_______________________________________________
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