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 SipEndSession-SysPost-Default {
run VolteSipAvpCdr
run MaxCallDuration
run SessionRefresh
}
|
Details
Feature script name |
VolteSipAvpCdr |
|---|---|
Applicable contexts |
SIP service |
SAS Support |
No |
Prerequisite features |
None, but information from various features is used if available |
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 |
|---|---|---|---|
TerminatingDomain |
String |
The accepted terminating domain in a T-ADS scenario |
MMTelWifiChargingFinalisation feature, SCCTADSParallelRouting feature |
MMTelInformation |
org.jainslee.resources.diameter .ro.types.vcb0.MmtelInformation |
The MMTel-Information Diameter AVP |
|
RegistrationRecords |
List<com.opencloud.sentinel.state.RegistrationRecord> |
Contains subscriber information retrieved from the Registrar and HSS or Cassandra |
|
CallReferenceNumber |
byte[] |
Contains the Call Reference Number used in queries to the HLR |
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.
|
