Re: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Controller p erspective)
Henning Schulzrinne <hgs@cs.columbia.edu> Sat, 07 September 2002 16:41 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15465 for <sip-archive@odin.ietf.org>; Sat, 7 Sep 2002 12:41:36 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g87GgmH29638 for sip-archive@odin.ietf.org; Sat, 7 Sep 2002 12:42:48 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87GbOX29288; Sat, 7 Sep 2002 12:37:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87Ga9X28729 for <sip@optimus.ietf.org>; Sat, 7 Sep 2002 12:36:09 -0400
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15287 for <sip@ietf.org>; Sat, 7 Sep 2002 12:34:27 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100]) by cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g87Ga0MK027537; Sat, 7 Sep 2002 12:36:00 -0400 (EDT)
Received: from cs.columbia.edu ([128.163.6.250]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g87GZxcD010304 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 7 Sep 2002 12:35:59 -0400 (EDT)
Message-ID: <3D7A2A9D.4020203@cs.columbia.edu>
Date: Sat, 07 Sep 2002 12:34:37 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rick W. Porter" <rporter@acmepacket.com>
CC: Jitender Arora <jarora@aastra.com>, sip@ietf.org
Subject: Re: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Controller p erspective)
References: <F924CEFBBF62D611A0C600D0B76ED03712FE7F@h3s68a245n132.user.nortelnetworks.com> <037001c25689$41841a40$2a00000a@RPORTER>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
See ipdr.org for another approach. (We also have a DIAMETER version for accounting: draft-narayanan-sipping-aaa-diameter-00.txt.) Comments on both would be most welcome. Unfortunately, while there are plenty of public-domain and commercial RADIUS servers, the number of DIAMETER servers seems to be approximately one. Rick W. Porter wrote: > Although it has expired, here is one draft you may find interesting: > > http://www.ietf.org/internet-drafts/draft-schulzrinne-sipping-radius-account > ing-00.txt > > There has been some discussion of whether RADIUS is the appropriate protocol > to use. The general consensus is that it is not ideal, but it is what some > providers have installed. However, I do not know what other drafts may be > available describing CDR generation. > > Good luck, > Rick > > ----- Original Message ----- > From: "Jitender Arora" <jarora@aastra.com> > To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com> > Cc: <sip@ietf.org> > Sent: Friday, September 06, 2002 4:51 PM > Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway > Controller p erspective) > > > >>Hi , >> >> could somebody please point to the draft or RFC which contains the >>information about how the >> CDR ( call detail records ) are generated for the SIP calls ( what > > all > >>informaion should be there >> in the CDR ) from the Media Gateway Controller Perspective . >> >> Is there any document available for this ...If yes please let me know >>.... >> >>Thanks and Regards, >>jitender . >>_______________________________________________ >>Sip mailing list https://www1.ietf.org/mailman/listinfo/sip >>This list is for NEW development of the core SIP Protocol >>Use sip-implementors@cs.columbia.edu for questions on current sip >>Use sipping@ietf.org for new developments on the application of sip >> > > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] Regarding SIP CDR inforamtion ( from a Medi… Jitender Arora
- Re: [Sip] Regarding SIP CDR inforamtion ( from a … Rick W. Porter
- Re: [Sip] Regarding SIP CDR inforamtion ( from a … Henning Schulzrinne
- RE: [Sip] Regarding SIP CDR inforamtion ( from a … Henry Sinnreich
- RE: [Sip] Regarding SIP CDR inforamtion ( from a … Cullen Jennings