Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Paul Kyzivat <pkyzivat@cisco.com> Thu, 29 September 2005 12:53 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EKxv5-0007ZB-3a; Thu, 29 Sep 2005 08:53:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EKxv0-0007Yo-T8
for sipping-tispan@megatron.ietf.org; Thu, 29 Sep 2005 08:53:49 -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 IAA08999
for <sipping-tispan@ietf.org>; Thu, 29 Sep 2005 08:53:44 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKy2e-0001Bl-1H
for sipping-tispan@ietf.org; Thu, 29 Sep 2005 09:01:42 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
by sj-iport-5.cisco.com with ESMTP; 29 Sep 2005 05:53:35 -0700
X-IronPort-AV: i="3.97,156,1125903600";
d="scan'208"; a="215759054:sNHT32046516"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
[64.102.31.102])
by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8TCrJ54002519;
Thu, 29 Sep 2005 05:53:29 -0700 (PDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
Thu, 29 Sep 2005 08:53:27 -0400
Received: from [161.44.79.87] ([161.44.79.87]) by xfe-rtp-202.amer.cisco.com
with Microsoft SMTPSVC(6.0.3790.211);
Thu, 29 Sep 2005 08:53:27 -0400
Message-ID: <433BE3C6.2030208@cisco.com>
Date: Thu, 29 Sep 2005 08:53:26 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Jesske, R" <R.Jesske@t-com.net>
Subject: Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
References: <E7666D92C64C2845AEF12636FF94F95203D1DB1D@S4DE8PSAAGQ.blf.telekom.de>
In-Reply-To: <E7666D92C64C2845AEF12636FF94F95203D1DB1D@S4DE8PSAAGQ.blf.telekom.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Sep 2005 12:53:27.0371 (UTC)
FILETIME=[C90799B0:01C5C4F4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: 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
Jesske, R wrote: > Dear Miguel and Mike, > The ETSI specification is based on Q.733.3. Within this specification it is described how a CCBS call can be rejected by the user B. > > ...For example if the destination local exchange knows that the CCBS is forbidden on the destination B user, then the diagnostic field shall be set to "CCBS not possible". Otherwise the diagnostic field shall be set to "CCBS possible".... > > So this describes if user be does not allows a CCBS call. This is a little hidden within the spec. But it is stated. So we can write such a requirement. So either we need such an indication "CCBS possible" or the CCBS request shall be rejected by the AS of the callee. I can't quite tell from this description, but it sounds like this covers the case where CCBS is universally forbidden at destination B. Does it also cover the case where user B decides on a case by case basis not to accept a CCBS from a particular caller, at a particular point in time? (This would require user B to be made aware of the CCBS when it is queued, rather than only when user B is alerted for the resulting call. Its not something that would easily be done on a black phone, but might be considered similar to call waiting.) Paul _______________________________________________ Sipping-tispan mailing list Sipping-tispan@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-tispan
- AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Schmidt, Christian
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- RE: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Michael Hammer (mhammer)
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Paul Kyzivat
- AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Schmidt, Christian
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Paul Kyzivat
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Jesske, R
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Paul Kyzivat