The MMTelStodEnabled feature checks if the subscriber has the STOD service provisioned .

Feature Cheat Sheet

B2BUA Instance SAS Support Originating / Terminating Point(s) in Session Plan Network Operator Data Subscriber Data Stateful or Stateless POJO Feature or SBB Feature Other notes

MMTel

No

Both

  • MMTelOrig_SipAccess_SubscriberCheck

  • MMTelTerm_SipAccess_SubscriberCheck

  • MMTel_Post_SipAccess_SubscriberCheck

  • MMTelOrig_SipAccess_PartyResponse

  • MMTelTerm_SipAccess_PartyResponse

  • MMTel_Pre_SipAccess_PartyResponse

Yes

Yes - subscriber data is from the HSS

Stateless

POJO Feature

Prerequisite Features

  • SubscriberDataLookupFromHssFeatureSbb

Session Input Variables

Session State variable name Type Comments
RegistrationRecords

Complex

List of registration records containing public id

Subscriber

String

subscriber id

Configuration

The configuration is stored in a JSLEE configuration profile with a profile table name of: MMTelStodEnabledConfigProfileTable. The profile is scoped by the Sentinel selection key and by the subscriber uri. Example : Opencloud:::::alice@opencloud.com.

Variable Name Type Constraint Default Default Value Interpretation Note
StodEnabled

Boolean

False

Indicates the subscriber is not allowed to use the STOD service

Session Output Variables

Session State variable name Type Comments
StodIsEnabledForUser

boolean

Set to true when Stod is enabled for the subscriber

AccessLegTrackingKeys

Set<String>

The set of external session tracking keys

AccessLegTrackingActive

boolean

Whether or not this session will be externally tracked

Statistics

Name Incremented when…​
Started

the feature runs

FailedToStart

Sentinel VoLTE encounters an error while attempting to start the feature

IssuedWarning

a non-fatal problem is encountered and the feature and issues a warning

FailedDuringExecution

a fatal problem is encountered and the feature cannot execute correctly

TimedOut

the feature takes too long to complete and Sentinel VoLTE aborts execution

StodIsEnabled

the Stod is enabled for a subscriber

StodIsNotEnabled

the Stod is not enabled for a subscriber

StodEnableSessionTracking

STOD session tracking is enabled for this session

StodSessionTrackingDisabled

STOD session tracking is disabled for this session

FoundTrackingKey

A tracking key has been created for this session and added to the set

Behaviour

The feature acts on INVITE requests and on responses.

On an INVITE request, the feature checks if the subscriber has the STOD service provisioned. For this, the IMPU is retrieved from registration data and matched with profile configuration. If the profile exists and the StodEnabled boolean variable is true, the feature sets the StodIsEnabledForUser session state field.

On responses, the feature checks to make sure that STOD session tracking has been enabled for the Served-User in the triggering message. In the event that the trigger is on a 200 (OK) response for an incoming INVITE request the feature will create a tracking key. The tracking key is taken from an IMPU in session state and the Tracking Key Prefix IMPU. The tracking key is then added to the External Session Tracking Keys. When there is no subscriber in session state or in the registration records there will be no IMPU in which case there will be no session tracking.

Source

For source code information see MMTel Session Transfer Source Code

Previous page Next page
Sentinel VoLTE Version 3.0.0