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

Tessa Silvia <Silvia.Tessa@TILAB.COM> Mon, 05 September 2005 11:27 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECF7u-0005NC-0r; Mon, 05 Sep 2005 07:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECF7s-0005N4-BK for sipping-tispan@megatron.ietf.org; Mon, 05 Sep 2005 07:27:00 -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 HAA11088 for <sipping-tispan@ietf.org>; Mon, 5 Sep 2005 07:26:59 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECFAd-0003kD-7h for sipping-tispan@ietf.org; Mon, 05 Sep 2005 07:29:51 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202]) by dns2.cselt.it (PMDF V6.1 #38895) with ESMTP id <0IMC0085UCGPIY@dns2.cselt.it> for sipping-tispan@ietf.org; Mon, 05 Sep 2005 13:12:25 +0200 (MEST)
Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01b.cselt.it with Microsoft SMTPSVC(6.0.3790.211); Mon, 05 Sep 2005 13:24:51 +0200
Date: Mon, 05 Sep 2005 13:26:47 +0200
From: Tessa Silvia <Silvia.Tessa@TILAB.COM>
Subject: R: [Sipping-tispan] [CCBS/CCNR]
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>, Miguel Garcia <Miguel.An.Garcia@nokia.com>, sipping-tispan@ietf.org
Message-id: <DCB4E22C68A78643A9550CC8E381128F01012B73@EXC01A.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Sipping-tispan] [CCBS/CCNR]
Thread-Index: AcWu4um+T6SzZUQ/QNOHd1bD6CeBdgAOspqAACTVQfAABVbHUACREmjg
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 05 Sep 2005 11:24:51.0703 (UTC) FILETIME=[6EBB0870:01C5B20C]
X-Spam-Score: 1.0 (+)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable
Cc:
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

Inline.
> >
> > Any time a user does not accept a session returned by CCBS
> > within a given timeslot his place in queue is removed, unless
> > he is busy.
> 
> First, I think the intent is still to have the CCBS requestor initiate
> the call, since there may be costs associated with doing so.

There's no cost issue related to who is initiating the call because the
network is able to bill the caller regardless if it is a first-party or
a third-party call.

> 
> Second, you suggestion may run into race conditions with the CCBS
> requestor attempting to send a suspend request, because perhaps he had
> to answer another incoming call.

A CCBS subscription can be suspended if and only if the caller is busy:
the caller can not say "I'm going out for 5 minutes, I'll suspend my
ccbs subscription, and resume it when I get back". The CCBS requestor
can not suspend and resume a request: he can only cancel it.

Does this exclude the race condition you mentioned ? If not, could you
explain a bit further? 

> 
> > Any time a user is busy when a session returned by CCBS is
> > delivered, he keeps his place in queue. Other users in queue,
> > if any, can be served.
> > (this last scenario is known as "suspension")
> >
> > Would that be ok ?
> 
> How does the called queue manager know whether the caller is busy or
> not?  I'm afraid these requirements are delving into the solution
> discussion, but I'm not sure if that is avoidable.


I'm afraid as well, but I'll try to answer by rephrasing requirement 1:
Req 1 declares the need to monitor the callee, actually there's also a
need to monitor the caller....

REQ-1:
The entity providing the CCBS/CCNR service needs to know the change of
the status of a UA (e.g., in CCBS a transition from busy to idle or in
CCNR a transition from idle to another state) and it should have the
ability to recognize if the UA is able to provide such indication.

I can't tell if UA is the correct term, what I want to say is that it
applies for both callee and caller.

Regards
Silvia


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
====================================================================

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