Project

General

Profile

Support #2360

Read CDR via CTRL interface in SGSN

Added by oramadan 5 months ago. Updated 17 days ago.

Status:
New
Priority:
Urgent
Assignee:
Target version:
-
Start date:
07/11/2017
Due date:
% Done:

40%

Spec Reference:

Description

How can you access per subscriber CDRs in the SGSN with either GETs or TRAPs(preferable)?


Related issues

Related to Cellular Infrastructure - Bug #2362: rate_ctr with name prefix containing "." not visible on CTRL interface Closed 07/11/2017

History

#1 Updated by laforge 4 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 40

The only capability related to CDR is the capability to write CDRs in CSV format. Related functionality is contained in http://git.osmocom.org/openbsc/tree/openbsc/src/gprs/sgsn_cdr.c which will write format like this:
"timestamp,imsi,imei,msisdn,cell_id,lac,hlr,event,pdp_duration,ggsn_addr,sgsn_addr,apni,eua_addr,vol_in,vol_out,charging_id\n"

It will write CDR records to a text file ("cdr filename NAME") in the following events:
  • gprs attach
  • routing area update
  • gprs detach
  • release of mm context
  • PDP context activation
  • PDP context deactivation
  • PDP context termination
  • PDP context release
  • periodically with a configurable timer ("cdr interval <1-2147483647>")

The internal statistics counters for per-MM-context and per-PDP-context in/out bytes and packets should be readable via the CTRL interface, but this is currenrly broken due to bad choice of naming, see #2362

#2 Updated by laforge 4 months ago

  • Related to Bug #2362: rate_ctr with name prefix containing "." not visible on CTRL interface added

#3 Updated by laforge 4 months ago

#4 Updated by laforge 4 months ago

laforge wrote:

The only capability related to CDR is the capability to write CDRs in CSV format. Related functionality is contained in http://git.osmocom.org/openbsc/tree/openbsc/src/gprs/sgsn_cdr.c which will write format like this:
"timestamp,imsi,imei,msisdn,cell_id,lac,hlr,event,pdp_duration,ggsn_addr,sgsn_addr,apni,eua_addr,vol_in,vol_out,charging_id\n"

Please also see chapter 9.4 of http://ftp.osmocom.org/docs/latest/osmosgsn-usermanual.pdf describing this feature.

#5 Updated by laforge 3 months ago

  • Status changed from In Progress to Feedback
  • Assignee changed from laforge to oramadan

How do we proceed here?

We have the existing CSV format support as described above. It would be relatively easy to add TRAPs in similar fashion, i.e. send the CSV line as a trap (rathe than a file write). But are the existing/stated triggers

gprs attach
routing area update
gprs detach
release of mm context
PDP context activation
PDP context deactivation
PDP context termination
PDP context release
periodically with a configurable timer ("cdr interval <1-2147483647>")

sufficient?

#6 Updated by laforge about 2 months ago

ping?

#7 Updated by oramadan about 1 month ago

Sorry for missing this! i recall working with the CSV was a little challenging if you want to rotate the file. Also the flexibility of sending over the network. The triggers and csv format you've described are great.

#8 Updated by laforge 26 days ago

  • Assignee changed from oramadan to sysmocom

#9 Updated by laforge 26 days ago

  • Priority changed from High to Urgent

#10 Updated by laforge 26 days ago

  • Status changed from Feedback to New

#11 Updated by laforge 17 days ago

  • Assignee changed from sysmocom to pespin

Also available in: Atom PDF