This feature reads charging settings from profile configuration and sets session state accordingly.
Details
Feature name |
DetermineCharging |
|---|---|
Applicable contexts |
SIP service |
SAS Support |
N/A |
Prerequisite features |
None |
Session State inputs and outputs
Inputs
| Name | Type | Purpose |
|---|---|---|
SentinelSelectionKey |
SentinelSelectionKey |
Used to select a configuration profile to load. |
Outputs
| Name | Type | Purpose |
|---|---|---|
DisableCharging |
boolean |
Flag indicating whether charging has been disabled for the session. |
InterimCdrsEnabled |
boolean |
Flag controlling whether interim CDRs will be created for the session. |
SessionCdrsEnabled |
boolean |
Flag controlling whether a session CDR will be created at the end of the session. |
ContinueCallOnOCSFailure |
boolean |
Flag controlling whether the session is permitted to continue if there is an OCS failure. |
MonitorCallOnly |
boolean |
Flag controlling whether online charging will be skipped. |
Configuration
This feature uses profile configuration to determine how each session state field should be set.
Configuration is kept in a profile table called DetermineChargingConfigProfileTable and profiles are scoped by Sentinel Selection Key.
Each profile has the following fields:
| Name | Type | Description |
|---|---|---|
DisableCharging |
boolean |
If true, online charging will be disabled for sessions using this profile. |
InterimCdrsEnabled |
boolean |
If true, interim CDRs will be created while sessions using this profile are in progress. |
SessionCdrsEnabled |
boolean |
If true, session CDRs will be created at the end of sessions using this profile. |
ContinueCallOnOCSFailure |
boolean |
If true, sessions using this profile will be allowed to continue in the event of OCS failure. |
Feature Statistics
DetermineCharging statistics are tracked by the sentinel.sip SBB and can be found under the following parameter set:
SLEE-Usage → sentinel.sip service ID → sentinel.sip SBB ID → feature.DetermineCharging
| Name | Type | Description |
|---|---|---|
|
Counter |
Incremented when the feature is triggered. |
|
Counter |
Incremented when the feature fails to start. |
|
Counter |
Incremented when the feature fails while executing. |
|
Counter |
Incremented when the feature issues a warning. |
|
Counter |
Incremented when the feature times out during execution. |
Behaviour
When triggered this feature will attempt to retrieve a profile from the DetermineChargingConfigProfileTable using the current Sentinel Selection Key.
If it fails to find a profile, the feature ends without doing anything.
If a profile is found, the values for DisableCharging, InterimCdrsEnabled, SessionCdrsEnabled, and ContinueCallOnOCSFailure are mapped directly from their profile fields to their equivalent session output fields.
The effect of each field is outlined below.
Charging Enabled/Disabled
The DisableCharging field controls whether online charging should be enabled for the session.
When it is set to true the following behaviour is executed:
-
All reservation charging instances in the Charging Manager will be finalised.
-
The
MonitorCallOnlysession output field will be set totrue.
When the MonitorCallOnly session state field is true, feature execution scripts will skip over online charging features.
Interim CDRs
The InterimCdrsEnabled field controls whether interim CDRs will be written for a session.
This is done by checking the value of the field in feature executions scripts, and only executing the Interim CDR Feature if it is true.
Session CDRs
The SessionCdrsEnabled field controls whether a session CDR will be written when a session ends.
This is done by checking the value of the field in feature executions scripts, and only executing the appropriate AVP CDR feature if it is true.
In Sentinel Express deployments this affects execution of the AVP CDR Feature. In Sentinel VoLTE deployments this affects execution of the VoLTE SIP AVP CDR Feature.
Continue Call On OCS Failure
The ContinueCallOnOCSFailure field determines system behaviour when there is a problem communicating with the OCS.
When it is set to true the call will be allowed to continue in the event of an OCS failure, however:
-
No further online charging will occur for the session, even if communication with the OCS is re-established.
-
Rf and CDRs will continue to track the session.
-
OCS failure for a conference call will still result in the session ending (except for mid-session failures).
