Re: [Sipping] Progress on draft-jesske-sipping-etsi-ngn-reason-03

"Jesske, R" <R.Jesske@telekom.de> Tue, 01 July 2008 12:33 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 929F43A6D7F; Tue, 1 Jul 2008 05:33:19 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEC203A6D7B for <sipping@core3.amsl.com>; Tue, 1 Jul 2008 05:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbwZFfE0Fqiy for <sipping@core3.amsl.com>; Tue, 1 Jul 2008 05:33:16 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [217.6.95.237]) by core3.amsl.com (Postfix) with ESMTP id 38BB73A6FC6 for <sipping@ietf.org>; Tue, 1 Jul 2008 05:11:58 -0700 (PDT)
Received: from S4DE8PSAANQ.mitte.t-com.de (S4DE8PSAANQ.mitte.t-com.de [10.151.180.166]) by tcmail21.telekom.de with ESMTP; Tue, 1 Jul 2008 14:12:08 +0200
Received: from S4DE8PSAAQB.mitte.t-com.de ([10.151.229.13]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 1 Jul 2008 14:12:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 01 Jul 2008 14:12:05 +0200
Message-Id: <9886E5FCA6D76549A3011068483A4BD402D127F9@S4DE8PSAAQB.mitte.t-com.de>
In-Reply-To: <200807010137.m611bI7k031110@dragon.ariadne.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] Progress on draft-jesske-sipping-etsi-ngn-reason-03
Thread-Index: AcjbGwQu0aek5Ex/SFugGlBKA2J1UwAPgv1w
References: <9886E5FCA6D76549A3011068483A4BD402CA8FB4@S4DE8PSAAQB.mitte.t-com.de><F66D7286825402429571678A16C2F5EE0420A32F@zrc2hxm1.corp.nortel.com><9886E5FCA6D76549A3011068483A4BD402CA9134@S4DE8PSAAQB.mitte.t-com.de> <200807010137.m611bI7k031110@dragon.ariadne.com>
From: "Jesske, R" <R.Jesske@telekom.de>
To: Dale.Worley@comcast.net, sipping@ietf.org
X-OriginalArrivalTime: 01 Jul 2008 12:12:07.0775 (UTC) FILETIME=[AEA3C6F0:01C8DB73]
Subject: Re: [Sipping] Progress on draft-jesske-sipping-etsi-ngn-reason-03
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

I'll try to reword the requirements:

REQ-1:
It should be possible to support PSTN-SIP-PSTN scenarios where the reason of a call release can be transferred though the SIP domain without any loss of information and no change of reason. 
REQ-2: 
It should be possible to provide correct announcements to a SIP user based on the reason for call clearing within the PSTN network or the PSTN user.

Is that better?

Best Regards

Roland

> -----Ursprüngliche Nachricht-----
> Von: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] Im Auftrag von 
> Dale.Worley@comcast.net
> Gesendet: Dienstag, 1. Juli 2008 03:37
> An: sipping@ietf.org
> Betreff: Re: [Sipping] Progress on 
> draft-jesske-sipping-etsi-ngn-reason-03
> 
> 
>    From: "Jesske, R" <R.Jesske@telekom.de>
> 
>    REQ-GEN-1:  
> 
>       All simulation services must provide interoperability with the 
>       PSTN/ISDN. By interoperability we mean that, in the case that a 
>       simulation or supplementary service is provided to one 
> of the users 
>       when one of the endpoints is located in the PSTN and 
> the other is 
>       located in the NGN IMS network, the user should receive 
> the service 
>       without any degradation as if the service were provided 
> in the native
>       network. 
>    
> I'll warn you that this requirement statement is (from a SIP point of
> view) extremely vague, and you're not likely to get any traction from
> it.
> 
>    So the Reason header within responses will help to fulfil 
> this there are
>    certain cause values that are very specific for services. Like the
>    example within the draft pointing to the Closed User Group service.
>    
> It seems to me that what you are seeking is not the ability to carry a
> certain list of ISUP cause values (e.g., the ones listed in the I-D),
> but rather a means for carrying the ISUP cause value itself, a way to
> tunnel the ISUP cause value.in SIP, for SS7-SIP-SS7 double-gatewaying.
> 
> And if that's what you want, you should state it as a requirement.
> 
> Dale
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP