The MMTelStodTriggerAnchor feature handles the transfer request and route it to the previous bound session .
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 |
|---|---|---|---|---|---|---|---|---|
Stod |
No |
Originating |
|
Yes |
Yes - subscriber data is from the HSS |
Stateless |
SBB Feature |
Session Input Variables
| Session State variable name | Type | Comments |
|---|---|---|
RegistrationRecords |
Complex |
Registration Records contain the public IMPU |
Subscriber |
String |
The subscriber Id |
StodIsEnabledForUser |
boolean |
Is the STOD enabled ? |
Statistics
MMTelStodTriggerAnchor statistics are tracked by the sentinel.volte.sip SBB
and can be found under the following parameter set in REM:
SLEE-Usage → sentinel.volte.sip service → sentinel.volte.sip SBB → feature → MMTelStodTriggerAnchor
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.volte.sip,vendor=OpenCloud,version=4.0.0].SbbID[name=sentinel.volte.sip,vendor=OpenCloud,version=4.0.0].feature.MMTelStodTriggerAnchor"
| 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 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 |
FiredIncomingRequestEvent |
the transfer INVITE is sent to the session to be transfered. |
Behaviour
The feature handles the transfer request and route it to the previous bound session.
The feature retrieves the existing session based on the IMPU from the registration records and fires an internal event, routing the transfer request to the previous bound existing session. If the existing session is owned by another operational node in the cluster, the transfer request is proxied to that node. 3 == Source
For source code information see MMTel Session Transfer Source Code
