Re: [splices] INVOKE Actions Scope

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Sun, 17 July 2011 18:14 UTC

Return-Path: <rifatyu@avaya.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F411F21F85E2 for <splices@ietfa.amsl.com>; Sun, 17 Jul 2011 11:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.377
X-Spam-Level:
X-Spam-Status: No, score=-3.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eW3AlAC09Cnw for <splices@ietfa.amsl.com>; Sun, 17 Jul 2011 11:14:30 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1AD21F85E0 for <splices@ietf.org>; Sun, 17 Jul 2011 11:14:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvIAAEUmI07GmAcF/2dsb2JhbABSmC6PRHeIfKZ4AppBhV1fBJgEi1M
X-IronPort-AV: E=Sophos;i="4.67,218,1309752000"; d="scan'208";a="291214923"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 17 Jul 2011 14:14:29 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Jul 2011 14:12:39 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Sun, 17 Jul 2011 14:14:28 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Cullen Jennings <fluffy@cisco.com>, "splices@ietf.org" <splices@ietf.org>
Date: Sun, 17 Jul 2011 14:14:27 -0400
Thread-Topic: [splices] INVOKE Actions Scope
Thread-Index: Acww/2lIInU16D1MQoqzcynyzVKFbgQbxviAAGhnjjcAZ0TGcA==
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CF878BAB@DC-US1MBEX4.global.avaya.com>
References: <4CA2C4386DB56F4589D436E1C3C86F752230509C3B@DC-US1MBEX4.global.avaya.com> <AD0C7C55-811C-4932-AAAE-4F8780D30BE4@cisco.com>, <6369CB70BFD88942B9705AC1E639A33822CF6DED91@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5779@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5779@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [splices] INVOKE Actions Scope
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jul 2011 18:14:31 -0000

> -----Original Message-----
> From: Worley, Dale R (Dale)
> Sent: Friday, July 15, 2011 1:03 PM
> To: Shekh-Yusef, Rifaat (Rifaat); Cullen Jennings; splices@ietf.org
> Subject: RE: [splices] INVOKE Actions Scope
> 
> > From: Shekh-Yusef, Rifaat (Rifaat) [rifatyu@avaya.com]
> >
> > An action can manipulate the state of an INVITE-based dialog. The 
> > following are the only allowed actions:
> >
> >   1) Initiate:
> >      This action instructs the UA to send an INVITE with specific
> >      characteristics to a specific target.
> >      i.   Target: <AOR>
> >      ii.  Media: audio, video, or both
> >      iii. Direction: recvonly, sendonly, sendrecv
> 
> There are probably two flavors of Initiate:  One where the INVOKE 
> specifies a dial string and one where it specifies a URI.
> 
> >   3) Join:
> >      This action instructs the UA to join an existing dialog by
> >      sending an INVITE with Join header and with specific
> >      characteristics
> >      i.  Media: audio, video, or both
> >      ii. Direction: recvonly, sendonly, sendrecv
> 
> I don't think this is a separate operation.
> If the intention is to join *at a remote UA*, then this is just an 
> Initiate where the request-URI is "sip:foo@bar?Join=xyz".
> If the intention is to initiate a new dialog, but have it joined *at 
> this UA* with an existing dialog, it is a form of the Conference 
> operation.
> 
What I had in mind for join is described in the following example:
http://www.ietf.org/mail-archive/web/splices/current/msg00049.html


> >   5) Decline:
> >      This action instructs the UA to decline an incoming call by
> >      sending a 603 response
> 
> Please use a 4xx response!
> 
> See 
> http://tools.ietf.org/id/draft-worley-6xx-considered-harmful-00.txt
> 
"A response of this type [6xx] not only rejects the call but also
   requires the termination of all attempts to route the call to
   alternative destinations "

If a telemarketer is calling me and I want to decline his call, then this is exactly what I want.
Why do you think that this is a bad thing to do?


> >   6) Send to VM:
> >      This action instructs the UA to stop ringing and send the
> >      incoming call to the VM system by sending a 302 response.
> 
> This assumes that the phone knows the proper VM URI.  It also assumes 
> the user is configured so that the next destination of the call is a 
> voicemail system.
> 
Yeah, I need to add some parameters here.


> Aren't "Decline" and "Send to VM" related to the ACH proposals?
> 
ACH is to affect the proxy handling of these features, while this is for handling of these features on the phone.
Does this answer your comment?


> Dale