The MMTelBindAci feature connects the IMPU acquired from the subscriber registration to the existing ACI for the session transfer .
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 |
|
Yes |
Yes - subscriber data is from the HSS |
Stateless |
SBB Feature |
Implications on Charging for Forwarded calls |
Session Input Variables
| Session State variable name | Type | Comments |
|---|---|---|
RegistrationRecords |
Complex |
Registration Records contain the public IMPU |
Subscriber |
String |
The subscriber Id |
CallType |
Complex |
The sip call type |
StodIsEnabledForUser |
boolean |
Is the STOD enabled ? |
Statistics
MMTelBindAci 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 → MMTelBindAci
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.volte.sip,vendor=OpenCloud,version=2.9.0].SbbID[name=sentinel.volte.sip,vendor=OpenCloud,version=2.9.0].feature.MMTelBindAci"
| 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 |
BoundAciToImpu |
the ACI is bound to an this is incremented. |
UsedLinkedAciForBinding |
the triggering ACI is not used for binding, i.e the call is not MobileTerminating then the linked ACI is used. |
UsedTriggeringAciForBinding |
the call is a MobileTerminating call the Triggering ACI is used for binding. |
Behaviour
The feature connects the IMPU acquired from the subscriber registration to the existing ACI for the session transfer. The subscriber has to be provisioned for the service, otherwise the feature won’t bind the session. The feature will only bind the session if the 200 OK from the INVITE is received.
Source
For source code information see MMTel Session Transfer Source Code
