This feature is responsible for building a Call Detail Record that reflects the actions taken whilst processing a session.
It runs once when a session is ending and creates a CDR based on information
gathered from session state, and then writes it out using the cdr-ra
.
By default, Sentinel runs featurescript PostEndSession { run IpsmgwAvpCdr } |
Feature cheat sheet
Feature Name | Network Operator Data | Used in PlanId(s) | Stateful or Stateless | POJO Feature or SBB Feature |
---|---|---|---|---|
IpsmgwAvpCdr |
No |
N/A |
Stateless |
POJO |
Session state inputs and outputs
Inputs
If any of these fields are unset the feature will skip writing them to the CDR file.
This feature uses the same session state fields as the Sentinel SIP AVP CDR feature. This page will only discuss the additions to the fields described there.
Name | Type | Description | Where set |
---|---|---|---|
SubmitReportType |
Enumerated |
The submit report type for the |
|
MSISDN |
String |
The MSISDN of a subscriber |
Fetch Routing Info Cassandra feature, MO Submission feature, SMMA Response feature, Store Routing Info Cassandra feature |
IMSI |
String |
The IMSI of a subscriber |
|
MTCorrelatedId |
String |
The MT correlated ID |
Fetch Routing Info Cassandra feature, Generate MT Correlation Id feature |
PSDeliveryStatus |
Enumerated |
The PS delivery status; one of |
|
CSDeliveryStatus |
Enumerated |
The CS delivery status; one of |
|
Impu |
String |
The IMPU of a subscriber |
|
OrigSccpAddress |
String |
The origination SCCP address of a call |
|
DestSccpAddress |
String |
The destination SCCP address of a call |
Functionality
This features uses the information from the session state fields mentioned above and constructs a protobuf message out of it for output. See AVP CDR Format for the format of these messages.
Also see Charging Information for general information about the contents of CDRs and CCRs.
This feature only supports writing binary CDRs. If the cdr-ra is
configured to write string CDRs the feature will fail to execute.
|