RE: [Sipping-tispan] Requirements -02h

"Michael Hammer \(mhammer\)" <mhammer@cisco.com> Fri, 30 September 2005 15:38 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELMyF-0006n3-Nw; Fri, 30 Sep 2005 11:38:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELMyE-0006mV-TX for sipping-tispan@megatron.ietf.org; Fri, 30 Sep 2005 11:38:47 -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 LAA17012 for <sipping-tispan@ietf.org>; Fri, 30 Sep 2005 11:38:44 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELN67-00009x-Uz for sipping-tispan@ietf.org; Fri, 30 Sep 2005 11:46:56 -0400
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 30 Sep 2005 08:38:37 -0700
X-IronPort-AV: i="3.97,162,1125903600"; d="scan'208"; a="216091274:sNHT51847846"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j8UFcYVt000046; Fri, 30 Sep 2005 08:38:34 -0700 (PDT)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 30 Sep 2005 11:37:42 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping-tispan] Requirements -02h
Date: Fri, 30 Sep 2005 11:37:41 -0400
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E39C9F6D@xmb-rtp-20b.amer.cisco.com>
Thread-Topic: [Sipping-tispan] Requirements -02h
Thread-Index: AcXF0kKUYg+LwRFoSXGXYLXdm3339AAAdycA
From: "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
To: "Paul Kyzivat \(pkyzivat\)" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 30 Sep 2005 15:37:42.0958 (UTC) FILETIME=[E5D494E0:01C5C5D4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Content-Transfer-Encoding: quoted-printable
Cc: sipping-tispan@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

Paul,

This would suggest that so long as one terminal belonging to the AoR has
the capability to accept another call *and* that terminal was recently
used by the user (hopefully the correct human), an attempt should be
made to complete using that terminal (plus any terminal that can accept
a call independent of activity - could be broadcast to all).

Boy, hope that presence system is smart.

Mike


> -----Original Message-----
> From: Paul Kyzivat (pkyzivat) 
> Sent: Friday, September 30, 2005 11:19 AM
> To: Michael Hammer (mhammer)
> Cc: Elwell, John; Miguel Garcia; sipping-tispan@ietf.org; 
> Alexeitsev, D
> Subject: Re: [Sipping-tispan] Requirements -02h
> 
> I think there can be no reasonable way to know if there is 
> another person available to take another call. So I think the 
> attempt must be made, and if there is no answer, then the 
> request requeued to be tried later.
> 
> Note that even when there is but a single user, some UAs 
> might be "busy" 
> (in a session) yet the user may be able to take the call:
> - the "busy" UA is doing IM. The user can still pick up a phone.
> - the user considers the CCBS more important. he will preempt
>    the call he is on to take the CCBS recall.
> 
> The latter case can happen with a single UA. (Its a call 
> waiting case.) So, contrary to the CCBS spec, I think the 
> recall should be offered in this case.
> 
> 	Paul
> 
> Michael Hammer (mhammer) wrote:
> > This appears to be a consequence of the multi-terminal 
> status union, 
> > meaning that some centralized entity (could be co-located with one
> > terminal) would need to keep track of the call state of all the 
> > terminals representing that user (AoR).  If any one of 
> those terminal 
> > is busy, then the caller is busy.  Only when all terminals 
> are unbusy, 
> > then the caller is deemed free to participate in the call 
> completion.
> > 
> > That assumes that only one human uses all the terminals.  If it is 
> > possible for more than one person to use those terminals, 
> there could 
> > be a problem.  Picture the teenage daughter (son) yacking 
> away while 
> > the father (mother) is trying to use CCBS to complete an 
> important call.
> > How one sets up the relationship from terminals to AoRs can 
> be tricky.
> > Perhaps some indication of CCBS from this terminal only 
> would be useful.
> > 
> > At least that is how I am interpreting the requirements.
> > 
> > Mike
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: sipping-tispan-bounces@ietf.org 
> >>[mailto:sipping-tispan-bounces@ietf.org] On Behalf Of Elwell, John
> >>Sent: Friday, September 30, 2005 8:49 AM
> >>To: Miguel Garcia; 'sipping-tispan@ietf.org'
> >>Cc: Alexeitsev, D
> >>Subject: RE: [Sipping-tispan] Requirements -02h
> >>
> >>Miguel,
> >>
> >>"REQ-CCBS/CCNR-15: Should the caller be busy at the time of 
> executing
> >>                     CCBS/CCNR request, the request is 
> suspended until
> >>                     its status changes (back to free status)."
> >>
> >>What is meant by caller busy? Is this the human user (or 
> application)? 
> >>Or the UA from which CCBS/CCNR was requested?
> >>Or all the caller's UAs? Or any of the caller's UAs? This 
> is important 
> >>as it will determine the SIP signalling needed to determine whether 
> >>the caller is busy.
> >>
> >>John
> >>
> >>
> >>>-----Original Message-----
> >>>From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com]
> >>>Sent: 30 September 2005 11:00
> >>>To: 'sipping-tispan@ietf.org'
> >>>Cc: Alexeitsev, D
> >>>Subject: [Sipping-tispan] Requirements -02h
> >>>
> >>>ok, so here it goes with a new iteration:
> >>>
> >>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> >>>g-tispan-requirements-02h.txt
> >>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> >>>g-tispan-requirements-02h.html
> >>>
> >>>And the diff version:
> >>>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> >>>g-tispan-requirements-02g-to-h.html
> >>>
> >>>Changes:
> >>>- Clarification that we don't list every single 
> requirement that we 
> >>>have.
> >>>- Calling Party Category requirements are now in the 
> general section
> >>>- New CCBS/CCNR requirements for the callee to be able to reject a 
> >>>request for the service and to be able to use any given terminal.
> >>>- Clear of ACR text related to the override feature.
> >>>
> >>>Note that I am still trying to classify my e-mail. Since
> >>
> >>you all have
> >>
> >>>been very active in the last few days, I wouldn't be
> >>
> >>surprise to see
> >>
> >>>that I have forgotten to add or modify something that has
> >>
> >>been agree
> >>
> >>>upon. In such case, please drop me an e-mail and I will add
> >>
> >>it in the
> >>
> >>>next iteration.
> >>>
> >>>/Miguel
> >>>-- 
> >>>Miguel A. Garcia           tel:+358-50-4804586
> >>>sip:miguel.an.garcia@openlaboratory.net
> >>>Nokia Research Center      Helsinki, Finland
> >>>
> >>>
> >>>_______________________________________________
> >>>Sipping-tispan mailing list
> >>>Sipping-tispan@ietf.org
> >>>https://www1.ietf.org/mailman/listinfo/sipping-tispan
> >>>
> >>
> >>_______________________________________________
> >>Sipping-tispan mailing list
> >>Sipping-tispan@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/sipping-tispan
> >>
> > 
> > 
> > _______________________________________________
> > Sipping-tispan mailing list
> > Sipping-tispan@ietf.org
> > https://www1.ietf.org/mailman/listinfo/sipping-tispan
> > 
> 

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan