R: [Sipping-tispan] [CCBS/CCNR]
Tessa Silvia <Silvia.Tessa@TILAB.COM> Fri, 02 September 2005 11:20 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EB9aq-0002ks-V1; Fri, 02 Sep 2005 07:20:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EB9ao-0002in-Sx
for sipping-tispan@megatron.ietf.org; Fri, 02 Sep 2005 07:20:22 -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 HAA29480
for <sipping-tispan@ietf.org>; Fri, 2 Sep 2005 07:20:21 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EB9cw-0006fq-6U
for sipping-tispan@ietf.org; Fri, 02 Sep 2005 07:22:35 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
by dns1.cselt.it (PMDF V6.0-025 #38895)
with ESMTP id <0IM600I37SOFWX@dns1.cselt.it> for
sipping-tispan@ietf.org; Fri, 02 Sep 2005 13:17:03 +0200 (MEST)
Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01a.cselt.it with
Microsoft SMTPSVC(6.0.3790.211); Fri, 02 Sep 2005 13:23:49 +0200
Date: Fri, 02 Sep 2005 13:19:48 +0200
From: Tessa Silvia <Silvia.Tessa@TILAB.COM>
Subject: R: [Sipping-tispan] [CCBS/CCNR]
To: sipping-tispan@ietf.org
Message-id: <DCB4E22C68A78643A9550CC8E381128F01012B5A@EXC01A.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Sipping-tispan] [CCBS/CCNR]
Thread-Index: AcWu4tVCR8+10prpSdmPzRs37GfeiQAA6BjAADI7JhA=
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 02 Sep 2005 11:23:49.0031 (UTC)
FILETIME=[CA22CB70:01C5AFB0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Content-Transfer-Encoding: quoted-printable
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 everybody, some answers / comments inline. > > Some additional questions / comments: > - Are CCBS / CCNR related to a terminal or an AOR of caller/callee? AOR > - A more precise definition of state change is needed (e.g. using BYE or > INVITE for a call, avoiding busy/idle expression) can't we refer to a user dialog state changes ? > - What is the meaning of "the callee showed activity"? Could this be WWW > search as well? A www activity would be "new stuff" therefore really good in my opinion, But I don't know if the requirements agree ... Otherwise, if the activity must be related to INVITE sessions only, we could rephrase with "the callee starts an outgoing communication or accepts an incoming communication". > - A message toward the caller about state change of the callee is missing What about: The CCBS/CCNR simulation service should be able to deliver a communication to the caller, when the callee becomes free. > - Are multiple request possible for CCNR as with CCBS? Yes, so the introduction could simply change into: It is possible for the caller to request several communications to be under the CCBS/CCNR requested status. Also the callee can be subject to several CCBS/CCNRS communications from different callers. Additionally, the service provides queue management to arbitrate several CCBS/CCNR requests to the same callee. > - Is it possible for a caller to have simultaneous CCBS and CCNR requests? It is technically possible, towards different callees obviously. There's a limit on the total number of outstanding CCBS and CCNR request. In some country (Italy for instance) this limit is 1, but in other it can be higher: so if the limit is 3, you can have 2 CCBS and a CCNR, just to give an example. Probably, this should be added in the service description. > - If a CCBS / CCNR request is cancelled from the network, should the > caller be informed? Actually that's not a requirement: in PSTN/ISDN there was not such requirement (possibility?) here I believe we are free to choose. Regards Silvia > -----Ursprüngliche Nachricht----- > Von: sipping-tispan-bounces@ietf.org [mailto:sipping-tispan- > bounces@ietf.org] Im Auftrag von Miguel Garcia > Gesendet: Donnerstag, 1. September 2005 11:19 > An: sipping-tispan@ietf.org > Betreff: [Sipping-tispan] [CCBS/CCNR] > > > Hi: > > with respect the added CCBS/CCNR requirements, I think something is > still missing. > > - A bit more elaboration on the queue management, precisely, what are > the implications for the service (I think there is the concept of a > "timeslot" in which a user can return a call, and if it doesn't happen, > the user misses his turn in the queue ... or somethign like that. > - A definition of a "CCBS/CCNR request", which at the moment, misleads > me in the interpretation of the service. It can mean two different > things: "Please add me to the CCBS/CCNR queue of the callee", or "this > is a session returned as a result of an indication from CCBS/CCNR". > - Perhaps and explanation that the queue manager must be able to > distinguish between "call in return to CCBS/CCNR free indication" from > regular calls. This is related to the "timeslot" concept as well. > > Anyone with further information of the requirements, please comment. > > /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 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
- R: [Sipping-tispan] [CCBS/CCNR] Tessa Silvia
- R: [Sipping-tispan] [CCBS/CCNR] Tessa Silvia
- Re: R: [Sipping-tispan] [CCBS/CCNR] Miguel Garcia
- R: [Sipping-tispan] [CCBS/CCNR] Tessa Silvia
- R: [Sipping-tispan] [CCBS/CCNR] Tessa Silvia
- Re: R: [Sipping-tispan] [CCBS/CCNR] Miguel Garcia
- Re: R: [Sipping-tispan] [CCBS/CCNR] Paul Kyzivat
- RE: R: [Sipping-tispan] [CCBS/CCNR] Drage, Keith (Keith)
- RE: R: [Sipping-tispan] [CCBS/CCNR] Elwell, John