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

Feature Cheat Sheet

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

MMTel

Both

  • MMTelOrig_SipAccess_SubscriberCheck

  • MMTelTerm_SipAccess_SubscriberCheck

Yes

Yes - subscriber data is from the HSS

Stateless

SBB 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

Statistics

Name Incremented when…​
StodIsEnabled

the Stod is enabled for a subscriber

StodIsNotEnabled

the Stod is not enabled for a subscriber

Behaviour

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

The feature acts on INVITE request and 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.

Source

For source code information see MMTel Session Transfer Source Code

Previous page Next page
Sentinel VoLTE Version 2.7.0