R: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Tessa Silvia <Silvia.Tessa@TILAB.COM> Thu, 29 September 2005 15:34 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EL0Qy-0003DF-Bg; Thu, 29 Sep 2005 11:34:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EL0Qw-0003DA-Gv
for sipping-tispan@megatron.ietf.org; Thu, 29 Sep 2005 11:34:54 -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 LAA18944
for <sipping-tispan@ietf.org>; Thu, 29 Sep 2005 11:34:51 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EL0YZ-0005PO-26
for sipping-tispan@ietf.org; Thu, 29 Sep 2005 11:42:51 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
by dns2.cselt.it (PMDF V6.1 #38895)
with ESMTP id <0INL008694LNRL@dns2.cselt.it> for
sipping-tispan@ietf.org; Thu, 29 Sep 2005 17:34:35 +0200 (MEST)
Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01b.cselt.it with
Microsoft SMTPSVC(6.0.3790.211); Thu, 29 Sep 2005 17:32:25 +0200
Date: Thu, 29 Sep 2005 17:34:34 +0200
From: Tessa Silvia <Silvia.Tessa@TILAB.COM>
Subject: R: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
To: Tom-PT Taylor <taylor@nortel.com>,
GARCIN Sebastien RD-CORE-ISS <sebastien.garcin@francetelecom.com>
Message-id: <DCB4E22C68A78643A9550CC8E381128F01012C53@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] Re: CCBS/CCNR in Version -02f
Thread-Index: AcXE/E3o8xl/OgROSKe8QwcegpqneQADDdjQ
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 29 Sep 2005 15:32:25.0812 (UTC)
FILETIME=[FE623140:01C5C50A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: abda3837e791065a13ac6f11cf8e625a
Content-Transfer-Encoding: quoted-printable
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
Hi, Hoping that I've correctly interpreted the whole discussion, I believe that the ccbs service requested by a terminal should be active for every device the calling user is registered to (even if it's no PSTN requirement, I suppose it is reasonable requirement). Moreover, if a user does the following actions, in order: 1) request ccbs 2) unregister 3) registers back from another location... ... should the CCBS service still work for him ? My personal answer is yes, actually this issue seems more important than the previous one. What I haven't understood from the discussion is the outcome, is it a requirement ? If so, would it be okay to add/modify a requirement as: When the service-specific condition related to the callee's state is met, the CCBS/CCNR service must be able to reach the caller at any of his locations. Otherwise, forget it :) Regards silvia > -----Messaggio originale----- > Da: Tom-PT Taylor [mailto:taylor@nortel.com] > Inviato: giovedì 29 settembre 2005 15.46 > A: GARCIN Sebastien RD-CORE-ISS > Cc: Elwell, John; Miguel Garcia; Michael Hammer (mhammer); Tessa Silvia; > sipping-tispan@ietf.org > Oggetto: Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > > Paul has already given his response to the substance of John's question, > but I thought I would try to make it clearer to you. Suppose the caller > has multiple devices, say a cell phone and a fixed line, as possible > contacts, all through the same address of record. John is asking > whether the call returned by CCBS must come back to the cell phone if > that is where the original call came from, or whether any of the devices > associated with that address of record could receive the return call. > > GARCIN Sebastien RD-CORE-ISS wrote: > > John, > > > > I am not sure I understand your question. I assume you are asking about > how the O-AS gets the calling party issue the CCBS/CCNR recall or ...? > > > > If this is the case, we are studying several possibilities (3rd party > call, REFER...) in TISPAN but none of them have SIP extension > requirements. > > > > Could you please be more specific as to what requirement you feel needs > to be captured? > > > > sébastien > > > > > > > > -----Message d'origine----- > > De : Elwell, John [mailto:john.elwell@siemens.com] > > Envoyé : jeudi 29 septembre 2005 14:22 > > À : GARCIN Sebastien RD-CORE-ISS; Miguel Garcia; Michael Hammer > (mhammer) > > Cc : Tessa Silvia; sipping-tispan@ietf.org > > Objet : RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > > > > Sebastien, > > > > Irrespective of the need for a service provider on the caller side, what > is the requirement concerning the call resulting from CCBS/CCNR - should > it use the same caller UA as that which issued the CCBS/CCNR request, or > should it use any UA registered as contact for the AoR concerned? > > > > John > > > > > > > >>-----Original Message----- > >>From: GARCIN Sebastien RD-CORE-ISS > >>[mailto:sebastien.garcin@francetelecom.com] > >>Sent: 29 September 2005 12:58 > >>To: Elwell, John; Miguel Garcia; Michael Hammer (mhammer) > >>Cc: Tessa Silvia; sipping-tispan@ietf.org > >>Subject: RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > >> > >>John, > >> > >>Basically it enables "service interactions", "charging model", > >>"control of subscriber rights to the service", "playing CCBS related > >>announcement"...Having the service logic embedded in an Application > >>Server serving the originating user makes all this possible. > >> > >>If you want a more detailed to understand the role of the service > >>provider acting of behalf of the caller, I suggest you read the > >>related section dealing with the originating exchange in ITU-T Q.733 > >>or contact your Siemens collegues that participate to TISPAN. > >> > >>Regards, > >>sébastien > >> > >> > >> > >> > >>-----Message d'origine----- > >>De : Elwell, John [mailto:john.elwell@siemens.com] Envoyé : jeudi 29 > >>septembre 2005 13:11 À : GARCIN Sebastien RD-CORE-ISS; Miguel Garcia; > >>Michael Hammer (mhammer) Cc : Tessa Silvia; sipping-tispan@ietf.org > >>Objet : RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > >> > >>Sebastien, > >> > >>I was not trying to open up an old debate. I was simply continuing the > >>recent debate about on whose behalf the service provider is acting, > >>and whether there are two service providers or one. I can see a role > >>for a service provider acting on behalf of the callee, since it needs > >>to look out for different UAs registered for the AoR concerned that > >>might be in a position to satisfy the CCBS/CCNR request. I am not sure > >>I understand what a service provider acting on behalf of the caller > >>would do. It would be good to get an answer to my question about > >>whether a CCBS/CCNR request results in a call from the same UA as that > >>from which the request was made or any UA registered as contact for > >>the caller's AoR. > >> > >>John > >> > >> > >> > >>>-----Original Message----- > >>>From: GARCIN Sebastien RD-CORE-ISS > >>>[mailto:sebastien.garcin@francetelecom.com] > >>>Sent: 29 September 2005 09:11 > >>>To: Elwell, John; Miguel Garcia; Michael Hammer (mhammer) > >>>Cc: Tessa Silvia; sipping-tispan@ietf.org > >>>Subject: RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > >>> > >>>John, > >>> > >>>You seems to want try and open the endless debate about where the > >>>intelligence should be placed in the network or in the > >> > >>terminals. The > >> > >>>approach you are proposing is not something that TISPAN > >> > >>will accept so > >> > >>>I suggest that we move out of this debate. > >>> > >>>sébastien > >>> > >>> > >>>-----Message d'origine----- > >>>De : sipping-tispan-bounces@ietf.org > >>>[mailto:sipping-tispan-bounces@ietf.org] De la part de Elwell, John > >>>Envoyé : jeudi 29 septembre 2005 08:20 À : Miguel Garcia; Michael > >>>Hammer (mhammer) Cc : Tessa Silvia; sipping-tispan@ietf.org Objet : > >>>RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > >>> > >>>Miguel, > >>> > >>>In-line, > >>> > >>>John > >>> > >>> > >>>>-----Original Message----- > >>>>From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com] > >>>>Sent: 28 September 2005 10:31 > >>>>To: Michael Hammer (mhammer) > >>>>Cc: Tessa Silvia; sipping-tispan@ietf.org > >>>>Subject: Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > >>>> > >>>>Hi Mike: > >>>> > >>>>Inline discussion. > >>>> > >>>>Michael Hammer (mhammer) wrote: > >>>> > >>>> > >>>>>Miguel, > >>>>> > >>>>>I think there is still a little bit of schizophrenia in the > >>>>>requirements. I assume that a server is acting on behalf > >>>> > >>>>of either the > >>>> > >>>>>caller or the callee, but not both because each could be > >>> > >>>served by a > >>> > >>>>>different host, domain, or organization. The first > >>>> > >>>>requirement seems to > >>>> > >>>>>assume that the CCBS is a terminating service of the > >>> > >>>callee. Other > >>> > >>>>>requirements seem to assume that the CCBS is a service of > >>>> > >>>>the caller. > >>>> > >>>>>Which is it? > >>>> > >>>>Both. It has been demonstrated that CCBS is a service > >> > >>that requires > >> > >>>>cooperation of both the originating and terminatine service > >>> > >>>providers. > >>> > >>>>This cooperation is mostly required to manage queues of both the > >>>>caller and callee, and to manage susped/resume states. > >>> > >>>[JRE] It is not clear to me what the involvement of the originating > >>>service provider is. Perhaps this comes down to what > >> > >>exactly are the > >> > >>>requirements for notifying the caller that a call may now > >> > >>succeed. Is > >> > >>>this notification constrained to go to the same UA that requested > >>>CCBS/CCNR in the first place, or should it go to any UA currently > >>>registered as a contact for the caller's AoR? In my opinion > >> > >>the former > >> > >>>is sufficient and indeed probably preferable. If I request > >> > >>CCBS/CCNR > >> > >>>from a particular UA I would expect to receive the notification on > >>>that same UA and make the new call attempt from there. In the > >>>relatively infrequent event that I move to a different UA in the > >>>intervening period, I could simply request CCBS/CCNR again from the > >>>new UA. > >>> > >>>So on the assumption that CCBS/CCNR involves only a single > >> > >>UA on the > >> > >>>caller side, what service does the originating service provider > >>>perform? Why can't the UA directly request CCBS/CCNR and > >> > >>communicate > >> > >>>with the service provider on the callee side to achieve this? The > >>>caller's UA will receive notification when a the call can > >> > >>be made and > >> > >>>can present that information to the caller somehow, allowing the > >>>caller to choose when to proceed with that call, e.g., whether to > >>>interrupt any ongoing communications in order to make that call. > >>> > >>> > >>>_______________________________________________ > >>>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] Re: CCBS/CCNR in Version -02f Tessa Silvia
- R: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Tessa Silvia
- Re: R: [Sipping-tispan] Re: CCBS/CCNR in Version … Miguel Garcia