The MMTelStodEnableSessionTracking feature adds the subscribers IMPU to the set of external session tracking keys .
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 |
|---|---|---|---|---|---|---|
MMTel |
Both |
|
Yes |
Yes - subscriber data is from the HSS |
Stateless |
POJO Feature |
Session Input Variables
| Session State variable name | Type | Comments |
|---|---|---|
Subscriber |
String |
The subscriber Id |
StodIsEnabledForUser |
boolean |
Session Transfer to Own Device is enabled for the subscriber |
Session Output Variables
| Session State Variable Name | Type | Contents |
|---|---|---|
External Session Tracking Keys |
Set<String> |
The set of external session tracking keys |
External Session Tracking Active |
boolean |
Whether or not this session will be externally tracked |
Statistics
| Name | Incremented when |
|---|---|
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 |
Behavior
The StodEnableSessionTracking 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.
