The MMTelStodBind feature connects the IMPU acquired from the subscriber registration to the existing ACI for the session transfer .

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_PartyResponse

  • MMTelTerm_SipAccess_PartyResponse

Yes

Yes - subscriber data is from the HSS

Stateless

SBB Feature

Implications on Charging for Forwarded calls

Prerequisite Features

  • SubscriberDataLookupFromHssFeatureSbb

  • MMTelStodEnabled

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

Name

Incremented when…​

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

Previous page Next page
Sentinel VoLTE Version 2.7.0