Cellular Infrastructure

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

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.

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?