Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Miguel Garcia <Miguel.An.Garcia@nokia.com> Mon, 03 October 2005 11:41 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EMOgy-0004f4-1Q; Mon, 03 Oct 2005 07:41:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EMOgu-0004ew-Ou
for sipping-tispan@megatron.ietf.org; Mon, 03 Oct 2005 07:41:09 -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>; Mon, 3 Oct 2005 07:41:07 -0400 (EDT)
Received: from mgw-ext02.nokia.com ([131.228.20.94])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMOpN-0004BS-1z
for sipping-tispan@ietf.org; Mon, 03 Oct 2005 07:49:53 -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
j93BeZ4G015298; Mon, 3 Oct 2005 14:40:35 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 3 Oct 2005 14:40:35 +0300
Received: from [127.0.0.1] ([172.21.35.218]) by esebh002.NOE.Nokia.com with
Microsoft SMTPSVC(5.0.2195.6881); Mon, 3 Oct 2005 14:40:35 +0300
Message-ID: <434118B3.6030104@nokia.com>
Date: Mon, 03 Oct 2005 14:40:35 +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: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
References: <50B1CBA96870A34799A506B2313F2667068BED4A@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F2667068BED4A@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 03 Oct 2005 11:40:35.0607 (UTC)
FILETIME=[44E85A70:01C5C80F]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mgw-ext02.nokia.com id
j93BeZ4G015298
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4824b9ef1b1988f2983d420e78cedc0a
Content-Transfer-Encoding: quoted-printable
Cc: Tessa Silvia <Silvia.Tessa@TILAB.COM>, 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 John: It should be part of the vesion -02h. http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sipping-tispan-requirements-02h.html Check out REQ-CCBS/CCNR-12 /Miguel Elwell, John wrote: > Jean-Marie, > > Thanks for your help. This needs to get reflected in the requirements (not > necessarily the susbscription option stuff, but the ability to be able to > send the recall notification to either the UA that requested CCBS/CCNR or to > all UAs). > > John > > > >>-----Original Message----- >>From: Stupka, Jean-Marie [mailto:jean-marie.stupka@siemens.com] >>Sent: 30 September 2005 08:58 >>To: Elwell, John; Paul Kyzivat; GARCIN Sebastien RD-CORE-ISS >>Cc: sipping-tispan@ietf.org; Tessa Silvia >>Subject: RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f >> >>John, >> >>ETSI EN 300 357 (V1.2.1): "Integrated Services Digital >>Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) >>supplementary service; Service description" says in subclause >>5.1, Provision/withdrawal: >> >>-- >>As a service provider option, the CCBS supplementary service >>can be offered with a subscription option which shall apply >>to the whole access of user A. The subscription option is >>detailed in Table 1. >> >>Table 1 >>Subscription option: Recall mode >>Values: >>- Global, i.e. CCBS recall offered to all terminals >>- Specific, i.e. CCBS recall offered to the terminal, which >>activated the CCBS supplementary service >> >>If the subscription option is not offered, one of the two >>values shall be chosen by the service provider. >>-- >> >>I believe this answers your question. >> >>Best regards, >>Jean-Marie >> >>-----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:47 AM >>To: Paul Kyzivat; GARCIN Sebastien RD-CORE-ISS >>Cc: sipping-tispan@ietf.org; Tessa Silvia >>Subject: RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f >> >>Exactly. We need to know the full set of requirements in >>order to select a >>protocol solution, and only then can we see whether we need >>any protocol >>extensions or not. So is it one UA or all UAs at the caller >>side that need >>to know that the callee is available? >> >>John >> >> >>>-----Original Message----- >>>From: Paul Kyzivat [mailto:pkyzivat@cisco.com] >>>Sent: 29 September 2005 17:44 >>>To: GARCIN Sebastien RD-CORE-ISS >>>Cc: sipping-tispan@ietf.org; Tessa Silvia >>>Subject: Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f >>> >>> >>> >>>GARCIN Sebastien RD-CORE-ISS wrote: >>> >>>>Paul, >>>> >>>>As far as I know there has been yet no firm decision from >>> >>>TISPAN on this particular point. >>> >>>>On this mailing list our efforts should focuse on getting >>> >>>the necessary SIP extension understood and agreed, the >>>competent body for taking service decisions is clearly not IETF. >>> >>>I have agreed with you on this. >>> >>> >>>>The problem we are discussing here requires no protocol >>> >>>extension and hence should not be inserted in the draft. >>> >>>But I don't know how you can say no protocol extension is required >>>without knowing what decision will be taken to this point. >>> >>>In general, I don't see how we can agree whether protocol >>>extensions are >>>required or not without understanding the definition of the service. >>> >>>In fact, I think one must consider the possible >>>implementations to the >>>service definition before one can decide that an extension is >>>or is not >>>needed. (One solution may require an extension, while another >>>solution >>>does not.) >>> >>>I am not happy with the way this exercise is going. It seems to be >>>trying to avoid stating the details of the service >>>requirements, or the >>>proposed solution, while stating requirements for extensions >>>needed for >>>some unstated solution. >>> >>>I think what we need is: >>> >>>1. a thorough statement of the how the feature is expected to >>> appear to users. (Not PSTN users, but users of sip >>>devices that have >>> the emulated services.) >>> >>>2. an outline of a proposed implementation (or alternative >>> implementations) >>> >>>3. a list of the requirements for currently nonexistent sip features >>> that prevent 2 from being implemented. >>> >>>4. specifications for new extensions that satisfy 2&3. >>> >>>I believe the very first submission came close to providing >> >>2&4, but >> >>>lacked 1&3. I had thought the intent was to provide 1, and >>>then to move >>>on to 2,3&4. But instead it seems like now the goal is to >>>just do 3&4, >>>without 1&2. >>> >>>I just don't see how we can make an informed decision on that basis. >>> >>> Paul >>> >>> >>>>sébastien >>>> >>>>-----Message d'origine----- >>>>De : Paul Kyzivat [mailto:pkyzivat@cisco.com] >>>>Envoyé : jeudi 29 septembre 2005 16:47 >>>>À : GARCIN Sebastien RD-CORE-ISS >>>>Cc : Tom-PT Taylor; Tessa Silvia; sipping-tispan@ietf.org >>>>Objet : Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f >>>> >>>> >>>> >>>>GARCIN Sebastien RD-CORE-ISS wrote: >>>> >>>> >>>>>Thanks for clarifying the question which is of interest but >>> >>>out of scope of the mailing list. >>> >>>>>I invite John and anybody else interested to participate to >>> >>>TISPAN meetings were those questions are debated. >>> >>>> >>>>I agree that debating which way TISPAN *wants* this to work >>> >>>is out of scope here. >>> >>>>But it seems there is still confusion about which choice >> >>TISPAN *has >> >>>>made* about this. That needs to be cleared up here. >>>> >>>>I'm now pretty sure that TISPAN wants all the caller's UAs >>> >>>to alert when it is time for the CCBS/CCNR request to be >>>completed, but I think my understanding of this is via >>>discussion rather than what is in the document. (I just >>>checked the -02g document and I can find nothing that states >>>which choice is intended.) >>> >>>>So I believe the document needs to be updated to reflect >>> >>>this in the description of the service, and via explicit >> >>requirements. >> >>>> Paul >>>> >>>> >>>> >>>>>sebastien >>>>> >>>>> >>>>>-----Message d'origine----- >>>>>De : Tom-PT Taylor [mailto:taylor@nortel.com] Envoyé : jeudi 29 >>>>>septembre 2005 15:46 À : GARCIN Sebastien RD-CORE-ISS Cc >> >>: Elwell, >> >>>>>John; Miguel Garcia; Michael Hammer (mhammer); Tessa Silvia; >>>>>sipping-tispan@ietf.org Objet : 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>>_______________________________________________ >>>>>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 >>> >> >>_______________________________________________ >>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
- [Sipping-tispan] CCBS/CCNR in Version -02f Schmidt, Christian
- [Sipping-tispan] Re: CCBS/CCNR in Version -02f Miguel Garcia
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f mhammer
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Miguel Garcia
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Michael Hammer (mhammer)
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Miguel Garcia
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Michael Hammer (mhammer)
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Tom-PT Taylor
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Michael Hammer (mhammer)
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Michael Hammer (mhammer)
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Michael Hammer (mhammer)
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Hans Erik van Elburg (RY/ETM)
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Stupka, Jean-Marie
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Miguel Garcia
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Elwell, John
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Paul Kyzivat
- Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Miguel Garcia
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Stupka, Jean-Marie
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f GARCIN Sebastien RD-CORE-ISS
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Drage, Keith (Keith)
- RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Drage, Keith (Keith)