[Iptel] WG: [Sipping] draft-mahy-iptel-cpc
"Jesske, R" <R.Jesske@telekom.de> Fri, 28 March 2008 14:04 UTC
Return-Path: <iptel-bounces@ietf.org>
X-Original-To: ietfarch-iptel-archive@core3.amsl.com
Delivered-To: ietfarch-iptel-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D26928C922; Fri, 28 Mar 2008 07:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.611
X-Spam-Level:
X-Spam-Status: No, score=-100.611 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, RDNS_NONE=0.1, 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 Ny4lUyzdGS84; Fri, 28 Mar 2008 07:04:35 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBBE228C10C; Fri, 28 Mar 2008 07:04:35 -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 BA49628C2CB for <iptel@core3.amsl.com>; Fri, 28 Mar 2008 07:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 qUbtUrkPEfo0 for <iptel@core3.amsl.com>; Fri, 28 Mar 2008 07:04:25 -0700 (PDT)
Received: from tcmail12.telekom.de (tcmail12.telekom.de [217.5.214.82]) by core3.amsl.com (Postfix) with ESMTP id A0B713A6E24 for <iptel@ietf.org>; Fri, 28 Mar 2008 07:04:24 -0700 (PDT)
Received: from s4de8psaans.mitte.t-com.de (s4de8psaans.mitte.t-com.de [10.151.180.168]) by tcmail11.telekom.de with ESMTP for iptel@ietf.org; Fri, 28 Mar 2008 15:04:23 +0100
Received: from S4DE8PSAAQB.mitte.t-com.de ([10.151.229.13]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Fri, 28 Mar 2008 15:04:23 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 28 Mar 2008 15:04:22 +0100
Message-Id: <9886E5FCA6D76549A3011068483A4BD4023298F5@S4DE8PSAAQB.mitte.t-com.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] draft-mahy-iptel-cpc
Thread-Index: AciP4AyvKryZizHZQY6C6ocMt54MXQAIlJywAAK4S+AAMbwRkAABXNtAAAB7UjAAAEGwcA==
From: "Jesske, R" <R.Jesske@telekom.de>
To: iptel@ietf.org
X-OriginalArrivalTime: 28 Mar 2008 14:04:23.0275 (UTC) FILETIME=[A01143B0:01C890DC]
Subject: [Iptel] WG: [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: multipart/mixed; boundary="===============0488648811=="
Sender: iptel-bounces@ietf.org
Errors-To: iptel-bounces@ietf.org
Hi, nevertheless what is the status now of cpc? Because cpc is needed in some cases like ieps of payphone. And we could add the OLI. Thanks and Best Regards Roland ________________________________ Von: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] Im Auftrag von DOLLY, MARTIN C, sbcuid Gesendet: Freitag, 28. März 2008 14:50 An: Sumit Garg; iptel@ietf.org; sipping@ietf.org Betreff: Re: [Sipping] draft-mahy-iptel-cpc Sumit, What is really needed is OLI & CPC for North American deployments. Prisons is an OLI value, not a CPC value. That is the issue with the cpc draft it mixes up two different parameters. OLI is what type of line, where CPC is call type ( for the most part). Martin ________________________________ From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf Of Sumit Garg Sent: Friday, March 28, 2008 9:13 AM To: iptel@ietf.org; sipping@ietf.org Subject: Re: [Sipping] draft-mahy-iptel-cpc I was surprised by the lack of responses. This is a real need as I believe intermediate exchanges could need special processing for calls from Prison etc. The reason I proposed using P-A-I as opposed to From header in the draft was: In case of anonymous calls, the From header is generally of the form anonymous@....... A derived tel-Uri with cpc would look like anonymous;cpc=payphone This violates the tel-URI syntax. P-Asserted-Id covers this scenario as well. If there is a defined standard mechanism for this requirement, could somebody please point me to the same? -Sumit "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- George Bernard Shaw From: iptel-bounces@ietf.org [mailto:iptel-bounces@ietf.org] On Behalf Of Sumit Garg Sent: Thursday, March 27, 2008 9:47 AM To: iptel@ietf.org; sipping@ietf.org Subject: Re: [Iptel] draft-mahy-iptel-cpc Over a period of time I have seen various efforts in that direction which eventually get dropped...to list a few: draft-schubert-sipping-saml-cpc-02.txt (Expired: jan 2007) draft-mahy-iptel-cpc-06.txt (Expired:Sep 2007) draft-ietf-sip-privacy-04.txt , Appendix A (Expired: 2002) draft-rocky-sipping-calling-party-category-01.txt (Expired : 2006) I've also seen implementation using parameters like isup-oli for which I could not even find a draft. Based on this I believe conveying CPC/OLI in SIP is a real requirement. Maybe for pure SIP scenario it could be done with caller-preferences, but not in interworking scenarios. From what I understand: 1. CPC in ISUP could be desired by the terminating exchange, however, the scope of the OLI is only 1 call-leg and could be different from CPC as it is more closely tied to the billing number. 3. CPC is ISUP only, OLI could be over MF also. I don't really care what the tag-name in use is (oli/cpc)but, from where I am looking I would say: 1. cpc-param in P-Asserted-Id corresponds to cpc in ISUP (Better than in From header as it is a tel-uri parameter). 2. cpc-param in History-Info/Diversion/P-DCS-Billing-Info/Referred-By etc. etc. could correspond to OLI. Is there some way of reaching consensus and moving on...rather than have more aborted attempts in the future? -Sumit "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- George Bernard Shaw From: iptel-bounces@ietf.org [mailto:iptel-bounces@ietf.org] On Behalf Of DOLLY, MARTIN C, ATTLABS Sent: Thursday, March 27, 2008 8:04 AM To: Lee, Yiu; iptel@ietf.org; rohan@ekabal.com Subject: Re: [Iptel] draft-mahy-iptel-cpc Yiu, There is not a standard way to pass CPC or OLI in SIP? Also, draft-mahy-iptel-cpc-06.txt would not meet Nroth American deployment needs because it blends CPC and OLI. Martin ________________________________ From: iptel-bounces@ietf.org [mailto:iptel-bounces@ietf.org] On Behalf Of Lee, Yiu Sent: Thursday, March 27, 2008 3:56 AM To: iptel@ietf.org; rohan@ekabal.com Subject: [Iptel] draft-mahy-iptel-cpc Hi, This draft (draft-mahy-iptel-cpc-06.txt) is expired. Will this draft become WG item? If not, is there any other standard way to carry CPC or OLI parameter in SIP? Thanks, Yiu
_______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel