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.
|
This feature is deprecated and not enabled by default. It has been superseded by the VoLTE SIP AVP CDR feature |
Details
Feature script name |
VolteSipLegacyCdr |
|---|---|
Applicable contexts |
SIP service |
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 Legacy 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 |
Statistics
VolteSipLegacyCdr statistics are tracked by the volte.sentinel.sip SBB
and can be found under the following parameter set in REM:
SLEE-Usage → volte.sentinel.sip service → volte.sentinel.sip SBB → feature → VolteSipLegacyCdr
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=volte.sentinel.sip,vendor=OpenCloud,version=2.7.0].SbbID[name=volte.sentinel.sip,vendor=OpenCloud,version=2.7.0].feature.VolteSipLegacyCdr"
| Name | Description |
|---|---|
Started |
Incremented each time the feature runs |
FailedToStart |
Incremented when a fatal error occurs before feature execution |
IssueWarning |
Incremented when a non fatal error occurs while the feature is executing |
FailedDuringExecution |
Incremented when a fatal error occurs while the feature is executing |
TimedOut |
Incremented when feature execution does not complete within a reasonable time frame |
CDRwritten |
Incremented when a CDR is written successfully |
CDRnotWritten |
Incremented when a CDR is not written successfully due to an error |
Functionality
This features uses the information from the session state fields mentioned above and constructs a protobuf message out of it for output. See Legacy 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.
|
