Re: [Iptel] [Sipping] draft-mahy-iptel-cpc

"DOLLY, MARTIN C, ATTLABS" <mdolly@att.com> Tue, 01 April 2008 12:46 UTC

Return-Path: <iptel-bounces@ietf.org>
X-Original-To: iptel-archive@megatron.ietf.org
Delivered-To: ietfarch-iptel-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B3C028C76B; Tue, 1 Apr 2008 05:46:58 -0700 (PDT)
X-Original-To: iptel@core3.amsl.com
Delivered-To: iptel@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADA4828C747; Tue, 1 Apr 2008 05:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.806
X-Spam-Level:
X-Spam-Status: No, score=-103.806 tagged_above=-999 required=5 tests=[AWL=2.793, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 KpalS1OcI5ct; Tue, 1 Apr 2008 05:46:56 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id 9DC1028D0AF; Tue, 1 Apr 2008 05:16:27 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-6.tower-121.messagelabs.com!1207052181!20990343!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 9095 invoked from network); 1 Apr 2008 12:16:22 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-6.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 1 Apr 2008 12:16:22 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m31CGLWH015175; Tue, 1 Apr 2008 08:16:21 -0400
Received: from OCCLUST04EVS1.ugd.att.com (ocst07.ugd.att.com [135.38.164.12]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m31CGG3s015146; Tue, 1 Apr 2008 08:16:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 01 Apr 2008 07:16:15 -0500
Message-ID: <28F05913385EAC43AF019413F674A0171246ED8B@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <C0E80510684FE94DBDE3A4AF6B968D2D03064C93@esealmw118.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] draft-mahy-iptel-cpc
Thread-Index: AciTT0huJkK+FBR7RpWeyPG2fMdD0gAhlBHQAAUtSrA=
References: <47F11654.6050607@cisco.com> <C0E80510684FE94DBDE3A4AF6B968D2D03064C93@esealmw118.eemea.ericsson.se>
From: "DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>
To: Ian Elz <ian.elz@ericsson.com>, iptel@ietf.org, sipping@ietf.org
Subject: Re: [Iptel] [Sipping] draft-mahy-iptel-cpc
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Telephony <iptel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/iptel>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: iptel-bounces@ietf.org
Errors-To: iptel-bounces@ietf.org

Ian,

CPC: Information sent in the forward direction indicating the category
of the calling party and, in case of semiautomatic calls, the service
language to be spoken by the incoming, delay and assistance operators.
The format of the calling party's category is shown below.

OLI:  Information sent in the forward direction indicating toll class of
service. Identification of the originating line.

Martin

-----Original Message-----
From: Ian Elz [mailto:ian.elz@ericsson.com] 
Sent: Tuesday, April 01, 2008 4:58 AM
To: Paul Kyzivat
Cc: iptel@ietf.org; DOLLY, MARTIN C, ATTLABS; sipping@ietf.org
Subject: RE: [Sipping] draft-mahy-iptel-cpc

Paul,

My comments are made based upon the content of the latest draft (06).

The introduction begins:

   "SS7 ISUP [4] defines a Calling Party's Category (CPC) parameter that
   characterizes the station used to originate a call and carries other
   important state that can describe the originating party.  When
   telephone numbers are contained in URIs, such as the tel URI [2], it
   may be desirable to communicate any CPC associated with that
   telephone number or, in the context of a call, the party calling from
   it."

Based upon this the current requirement appears to be to support the
ISUP CPC/OLI.

If the requirement is greater than this then that is a discussion that
we should have before the draft is finalized.

The issue with mutual exclusivity exists in the current ISUP
implementations. If that limitation is to be overcome then that
requirement also needs to be discussed. If we are to move from mutual
exclusivity of values then we need to ensure that interworking back to
ISUP is supported. The resolution of the overlapping cases as you have
indicated may have to be at the discretion of the network operator.

Ian Elz

_______________________________________________
Iptel mailing list
Iptel@ietf.org
https://www.ietf.org/mailman/listinfo/iptel