Sentinel Express 2.7.0 :: Sentinel Administration Guide

Description

Configuration name	Session Control
Applicable contexts	SS7 service

Configuration name

Session Control

Applicable contexts

SS7 service

The Session Control Configuration determines how the charging shall be controlled during the session and whether Apply Charging Reports or Call Information Reports shall be used when the charging session to the OCS is finalised.

Configuration

The default behaviour of Sentinel is to use Apply Charging Reports:

for controlling the charging for the duration for the session
when the CCR-T is sent to the OCS to finalise the credit control session.

The Session Control configuration includes:

Parameters Description

Parameters	Description
SessionControlMethod	Whether charging during the session shall be performed via internal SLEE Timer, via Apply Charging Reports from the MSC, or via Call Information Report once at the very end of the session. Valid options are: protocolDefault — Use a sensible default for the currently executing protocol. notControlled — Don’t control call duration. controlViaSleeTimer — Periodically perform charging queries based on configurable session timer. controlViaApplyCharging — Use `ApplyCharging` messages to drive charging interactions. Default for CAP session control. controlViaSleeTimerWithFinalACR — Send an initial `ApplyChargingRequest` and expect a final `ApplyChargingReport`. Use session timer to control charging interactions mid-call in the same way as controlViaSleeTimer. Default for CS1+ session control. controlViaCallInformationReport — Use CallInformationReport-based charging interaction method.
PreferredEndCallChargingEvent	Whether to use Apply Charging Report or Call Information Report for credit finalisation, in the case where both these events are available at call end. Valid options are: ‘useACR’, ‘useCIRp’.

SessionControlMethod

Whether charging during the session shall be performed via internal SLEE Timer, via Apply Charging Reports from the MSC, or via Call Information Report once at the very end of the session. Valid options are:

protocolDefault — Use a sensible default for the currently executing protocol.
notControlled — Don’t control call duration.
controlViaSleeTimer — Periodically perform charging queries based on configurable session timer.
controlViaApplyCharging — Use ApplyCharging messages to drive charging interactions. Default for CAP session control.
controlViaSleeTimerWithFinalACR — Send an initial ApplyChargingRequest and expect a final ApplyChargingReport. Use session timer to control charging interactions mid-call in the same way as controlViaSleeTimer. Default for CS1+ session control.
controlViaCallInformationReport — Use CallInformationReport-based charging interaction method.

PreferredEndCallChargingEvent

Whether to use Apply Charging Report or Call Information Report for credit finalisation, in the case where both these events are available at call end. Valid options are: ‘useACR’, ‘useCIRp’.

Configuration profile naming

Configuration Profile Table Name Description Profile Naming

Configuration Profile Table Name	Description	Profile Naming
SessionControlMethodTable	Service configuration	SentinelSelectionKey (for example, `OpenCloud::::`)

SessionControlMethodTable

Service configuration

SentinelSelectionKey (for example, OpenCloud::::)

Provisioning interfaces

The configuration can be provisioned using the Sentinel machine provisioning API — see SS7 Session Control REST API.

Previous page Next page