Re: [sipcore] Does SIP support "Reverse Charging" function?

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 25 September 2010 17:32 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 841153A697F; Sat, 25 Sep 2010 10:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level:
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[AWL=-1.675, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 QAN-LSsnx4ZO; Sat, 25 Sep 2010 10:32:55 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id B886D3A69B4; Sat, 25 Sep 2010 10:32:54 -0700 (PDT)
X-AuditID: c1b4fb3d-b7cbfae00000264e-39-4c9e3267d2e2
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id BC.D0.09806.7623E9C4; Sat, 25 Sep 2010 19:33:28 +0200 (CEST)
Received: from esessmw0191.eemea.ericsson.se (153.88.115.84) by esessmw0237.eemea.ericsson.se (153.88.115.90) with Microsoft SMTP Server (TLS) id 8.2.234.1; Sat, 25 Sep 2010 19:33:27 +0200
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.78]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Sat, 25 Sep 2010 19:33:27 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gao.yang2@zte.com.cn" <gao.yang2@zte.com.cn>
Date: Sat, 25 Sep 2010 19:31:29 +0200
Thread-Topic: [sipcore] Does SIP support "Reverse Charging" function?
Thread-Index: ActceBuVTFoptya0THWLAV+y/HtNhgAX2DOB
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585015BCAB2@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A058501653FA8@ESESSCMS0356.eemea.ericsson.se>, <OF5EE5D560.2B548D1A-ON482577A9.0020AA69-482577A9.00214052@zte.com.cn>
In-Reply-To: <OF5EE5D560.2B548D1A-ON482577A9.0020AA69-482577A9.00214052@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "sipcore@ietf.org" <sipcore@ietf.org>, "sipcore-bounces@ietf.org" <sipcore-bounces@ietf.org>
Subject: Re: [sipcore] Does SIP support "Reverse Charging" function?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2010 17:32:57 -0000

Hi,

I am not sure what more text you would need in 22.173.

What you need to do is to create a work item in CT1 in order to specify the protocol details.

Anyway, this is not the right forum to discuss this :)

Regards,

Christer

________________________________
From: gao.yang2@zte.com.cn [gao.yang2@zte.com.cn]
Sent: Saturday, September 25, 2010 9:01 AM
To: Christer Holmberg
Cc: DRAGE, Keith (Keith); sipcore@ietf.org; sipcore-bounces@ietf.org
Subject: RE: [sipcore] Does SIP support "Reverse Charging" function?


Hi Christer,

Do you mean this section in 22.173:

It is quit raw, and I didn't see any further progress for this topic.

Thanks,

Gao

8.2.16        Reverse charging

8.2.16.1        Definition

The reverse charging at communication set up time service allows the terminating party to be charged for the entire communication. Only usage based charges can be applied to the terminating party. The service shall be requested by the originating party at communication set up time. The terminating party must receive an explicit indication of a reverse charge communication request.

This service description is based on the service description described in [E-19].

8.2.16.2        Service interactions with other IMS supplementary services

None.

8.2.16.3        Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of Reverse Charging with the PSTN/ISDN and vice-versa.

===================================
Zip    : 210012
Tel    : 87211
Tel2   :(+86)-025-52877211
e_mail : gao.yang2@zte.com.cn
===================================


Christer Holmberg <christer.holmberg@ericsson.com>

2010-09-25 13:58


收件人
        "'gao.yang2@zte.com.cn'" <gao.yang2@zte.com.cn>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
抄送
        "sipcore@ietf.org" <sipcore@ietf.org>, "sipcore-bounces@ietf.org" <sipcore-bounces@ietf.org>
主题
        RE: [sipcore] Does SIP support "Reverse Charging" function?








Hi,

>I guess you(or ALU) would alos have reverse charging requirement for your deployed IMS network. Then, may us propose the requirement to the SA1 group, and then, SIP extension work in IETF?

The requirement already exists in SA1 (3GPP TS 22.173).

Regards,

Christer






--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.