Re: [Sipping-tispan] Requirements -02h

Miguel Garcia <Miguel.An.Garcia@nokia.com> Tue, 04 October 2005 12:22 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMloR-0002R7-Aw; Tue, 04 Oct 2005 08:22:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMloP-0002QN-7Z for sipping-tispan@megatron.ietf.org; Tue, 04 Oct 2005 08:22:25 -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 IAA14260 for <sipping-tispan@ietf.org>; Tue, 4 Oct 2005 08:22:23 -0400 (EDT)
Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMlx0-00077b-Uu for sipping-tispan@ietf.org; Tue, 04 Oct 2005 08:31:23 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j94CKMpF003517; Tue, 4 Oct 2005 15:20:25 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Oct 2005 15:21:37 +0300
Received: from [127.0.0.1] ([172.21.35.218]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 4 Oct 2005 15:21:36 +0300
Message-ID: <434273D1.2040900@nokia.com>
Date: Tue, 04 Oct 2005 15:21:37 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sipping-tispan] Requirements -02h
References: <072C5B76F7CEAB488172C6F64B30B5E39C9EEE@xmb-rtp-20b.amer.cisco.com> <43411B77.7070302@nokia.com> <4341340C.7080209@cisco.com>
In-Reply-To: <4341340C.7080209@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Oct 2005 12:21:36.0218 (UTC) FILETIME=[29F58BA0:01C5C8DE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Content-Transfer-Encoding: 7bit
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

Hi Paul:

Ok, your consideration about the globality of the response codes sounds 
reasonable. So then, a 6xx response code to a CCBS recall should be 
treated as a a request to abandom the queue forever, right?

/Miguel

Paul Kyzivat wrote:

> 
> 
> Miguel Garcia wrote:
> 
>> Yeap, I agree. I posted also a question as for a decline should have 
>> the same effect. There is currently no "decline" in PSTN, although it 
>> exists in mobile networks, and IMHO a decline to a ccbs recall should 
>> make the ccbs request to be placed as suspended.
> 
> 
> Hmm, what do you mean by "suspension"? Since 603 Decline is a Global 
> Failure, it should be interpretted as speaking for all the UAs. But I am 
> thinking this should be interpretted as a cancellation of the CCBS, 
> rather than a suspension. OTOH, I think 600 Busy Everywhere should be 
> treated literally - as if all the UAs had reported Busy Here - as an 
> indication to try later.
> 
>     Paul
> 
>> /Miguel
>>
>> 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
>>>
>>>
>>>
>>>
>>

-- 
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