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

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 25 September 2010 05:57 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 74EC93A69C5; Fri, 24 Sep 2010 22:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.567
X-Spam-Level:
X-Spam-Status: No, score=-5.567 tagged_above=-999 required=5 tests=[AWL=0.432, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, 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 iveYfzEr3RvH; Fri, 24 Sep 2010 22:57:32 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 6D3903A6964; Fri, 24 Sep 2010 22:57:31 -0700 (PDT)
X-AuditID: c1b4fb3d-b7cbfae00000264e-0b-4c9d8f6bedbe
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 71.45.09806.B6F8D9C4; Sat, 25 Sep 2010 07:58:03 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.78]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Sat, 25 Sep 2010 07:58:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "'gao.yang2@zte.com.cn'" <gao.yang2@zte.com.cn>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Sat, 25 Sep 2010 07:58:02 +0200
Thread-Topic: [sipcore] Does SIP support "Reverse Charging" function?
Thread-Index: ActccGG/RB5CVU+vT3eKme4hE+Nr0wABfkIg
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058501653FA8@ESESSCMS0356.eemea.ericsson.se>
References: <EDC0A1AE77C57744B664A310A0B23AE2173212E6@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <OFB59AC847.5C8BD073-ON482577A9.001BD2F5-482577A9.001CA1EB@zte.com.cn>
In-Reply-To: <OFB59AC847.5C8BD073-ON482577A9.001BD2F5-482577A9.001CA1EB@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "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 05:57:33 -0000

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