Re: [Sipping-tispan] [CCBS/CCNR]

Miguel Garcia <Miguel.An.Garcia@nokia.com> Tue, 06 September 2005 11:35 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECbjd-0006io-Se; Tue, 06 Sep 2005 07:35:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECbjc-0006iQ-Ij for sipping-tispan@megatron.ietf.org; Tue, 06 Sep 2005 07:35:28 -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 HAA22112 for <sipping-tispan@ietf.org>; Tue, 6 Sep 2005 07:35:27 -0400 (EDT)
Received: from mgw-ext02.nokia.com ([131.228.20.94]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECbmZ-0002GM-5h for sipping-tispan@ietf.org; Tue, 06 Sep 2005 07:38:32 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j86BZMaE017714; Tue, 6 Sep 2005 14:35:23 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 Sep 2005 14:35:12 +0300
Received: from [127.0.0.1] ([172.21.35.75]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 6 Sep 2005 14:30:54 +0300
Message-ID: <431D7DEC.8030405@nokia.com>
Date: Tue, 06 Sep 2005 14:30:52 +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] [CCBS/CCNR]
References: <072C5B76F7CEAB488172C6F64B30B5E382E1B8@xmb-rtp-20b.amer.cisco.com> <43183E94.8000801@nokia.com> <4318550A.6010605@cisco.com> <431BE6D0.90305@nokia.com> <431CB1FD.9000501@cisco.com>
In-Reply-To: <431CB1FD.9000501@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Sep 2005 11:30:54.0275 (UTC) FILETIME=[7140E130:01C5B2D6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit
Cc: sipping-tispan@ietf.org
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 Kyzivat wrote:


> 
>>>> With respect your question, then probably we need to define what "no 
>>>> reply" means, in which case, I would say that "no reply" is the 
>>>> event when the session is properly delivered to the callee never 
>>>> answers. Note that this has nothing to do with "no logged in", or 
>>>> any 4xx, 5xx, or 6xx responses. It just that, e.g., an INVITE is 
>>>> properly answered with a 1xx response, but no other response is 
>>>> received within a period of time.
>>>
>>>
>>> It could also be that there is no phone registered, which would 
>>> result in a 480 response. I think that probably should also be 
>>> considered a No-Response case.
>>
>>
>> I think the service is clearly focusing on the "no reply", so you are 
>> registered, but don't answer. If the phone is not registered, I think 
>> there can't be any completion of call, unless you subscribed to the 
>> presence information of the callee and monitor when he becomes 
>> registered.
> 
> 
> This is a case where the environments are so dissimilar that we need to 
> be careful to figure out what the proper analogy is.
> 
> In the case of analog phone service, if you unplug your phone and 
> someone calls I think it would be treated as a no-answer case. Now if 
> you switch to sip phones, and you unplug the phone, it will be a 
> not-registered case. From the caller's perspective the situation is the 
> same, and this is a primarily a caller facing feature. So I think this 
> should probably be part of the same service. I'd be interested to hear 
> other opinions.

That's true... I am also interested in hearing other opinions. But as I 
said before, in GSM and DECT (european cordless) there is a similar 
service call Call Forwarding on User Not-Logged In. So clearly the 
service separates the not-logged in feature from the no reply.

> 
> Watching the reg event package would then be required to know when to 
> try again. It would be an excellent indicator that someone is present to 
> respond. (Though not a perfect indicator. It could just be a device that 
> had power restored to it.)

Agree.

> 
> This isn't the only case that is going to require use of the reg event. 
> Use of the dialog package will also need the reg package to discover the 
> UAs at which a subscription to dialog is needed.
> 
>> There is a similar service, called Call Forwarding on not-logged in 
>> (or something similar), which is not applicable to the PSTN, but to 
>> mobile and cordless networks.
> 
> 
> I don't believe that is a similar service. It is more of a callee 
> oriented service - providing the callee with a backup service when their 
> primary device(s) aren't available.

True, it is a calee oriented service. My whole point is that there is a 
service that differentiates the states "no reply" from "not-logged in". 
Once you have differentiated the states, then you can apply services to 
the caller (Call complibation on...) or the callee (Call forwarding on...)

/Miguel


> 
>     Paul

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