AW: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
"Jesske, R" <R.Jesske@t-com.net> Fri, 30 September 2005 06:33 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1ELESJ-0006g9-1W; Fri, 30 Sep 2005 02:33:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1ELESG-0006fl-Vg
for sipping-tispan@megatron.ietf.org; Fri, 30 Sep 2005 02:33:13 -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 CAA23741
for <sipping-tispan@ietf.org>; Fri, 30 Sep 2005 02:33:12 -0400 (EDT)
Received: from tcmail33.telekom.de ([217.6.95.240])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELEa4-0004Zx-AA
for sipping-tispan@ietf.org; Fri, 30 Sep 2005 02:41:17 -0400
Received: from S4DE8PSAANQ.mitte.t-com.de by tcmail31.dmz.telekom.de with
ESMTP; Fri, 30 Sep 2005 08:33:02 +0200
Received: by S4DE8PSAANQ.blf.telekom.de with Internet Mail Service
(5.5.2653.19) id <T43W27RL>; Fri, 30 Sep 2005 08:33:02 +0200
Message-Id: <E7666D92C64C2845AEF12636FF94F95202319FA0@S4DE8PSAAGQ.blf.telekom.de>
From: "Jesske, R" <R.Jesske@t-com.net>
To: pkyzivat@cisco.com
Subject: AW: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Date: Fri, 30 Sep 2005 08:33:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
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
> -----Ursprüngliche Nachricht----- > Von: Paul Kyzivat [mailto:pkyzivat@cisco.com] > Gesendet: Donnerstag, 29. September 2005 14:53 > An: Jesske, Roland > Cc: Miguel.An.Garcia@nokia.com; mhammer@cisco.com; > Silvia.Tessa@TILAB.COM; sipping-tispan@ietf.org > Betreff: Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f > > > > > 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? Within the PSTN/ISDN it is a permanent status. But I think we can open it for the SIP service. We can use XCAP for provisioning purposes so the user can decide when he want to be reached by CCBS calls and when not. A call by call soultion is from my point of view not needed and wishful. Roland > > (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: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Schmidt, Christian
- AW: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Jesske, R