The MMTelTIP feature implements the Terminating Identification Presentation (TIP) service .
What is TIP?
From 3GPP TS 24.608:
The Terminating Identification Presentation (TIP) service provides the originating party with the possibility of receiving identity information in order to identify the terminating party. The network shall deliver the Terminating Identity to the originating party on communication acceptance regardless of the terminal capability to handle the information. |
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 |
Originating |
SipAccess_SubscriberCheck, and SipAccess_PartyResponse |
No |
Yes |
Source Code
This feature’s source code is available in the Sentinel VoLTE SDK in the mmtel-id-presentation-restriction module pack.
It can be viewed by using the create-module command in the SDK with that module pack, for example:
> create-module new-idpr-module opencloud#mmtel-id-presentation-restriction#volte/2.7.0;2.7.0.0
This command will prompt you for information needed to create the new modules, once completed the original source for the feature can be found in the new modules.
The module-pack includes the following modules relevant to this feature:
| Module Name | Description |
|---|---|
mmtel-id-presentation-restriction |
Group module for the feature that includes all of the modules listed below. |
mmtel-id-presentation-restriction-library |
Contains code shared by all ID presentation and restriction features. |
mmtel-tip-profile |
Contains the profile specification for the feature configuration profile table. |
mmtel-tip |
Contains the feature itself. |
Session input variables
TIP requires the following session state input variables:
| Variable name | Type | Comments |
|---|---|---|
Complex |
Read from the HSS or HLR in SubscriberDataLookupFromHSS or SubscriberDataLookupFromHLR |
|
APartyFromHeaderAnonymized |
boolean |
Used to determine whether the "from-change" tag needs to be removed from outgoing responses. |
Session output variables
| Variable name | Type | Comments |
|---|---|---|
RanTip |
boolean |
Signals to other features that TIP ran on this session. |
Statistics
MMTelTIP statistics are tracked by the volte.sentinel.sip SBB and can be found under the following parameter set:
SLEE-Usage → volte.sentinel.sip service → volte.sentinel.sip SBB
| Statistic | Incremented when… |
|---|---|
MMTelTIPFeatureStarted |
the feature runs |
MMTelTIPFeatureFailedToStart |
sentinel VoLTE encounters an error while attempting to start the feature |
MMTelTIPFeatureIssuedWarning |
a non-fatal problem is encountered and the feature and issues a warning |
MMTelTIPFeatureFailedDuringExecution |
a fatal problem is encountered and the feature cannot execute correctly |
MMTelTIPFeatureTimedOut |
the feature takes too long to complete and Sentinel VoLTE aborts execution |
MMTelTIPFeatureProcessingResponse |
the feature processes a SIP response |
MMTelTIPFeatureProcessingRequest |
the feature processes a SIP request |
MMTelTIPFeatureOverrideCategoryTriggered |
the feature disregards requested privacy settings on an incoming SIP message (due to the subscriber having override category status) |
MMTelTIPFeatureFromChangeTagRemoved |
the feature removes the |
MMTelTIPFeaturePrivacyHeaderChanged |
the feature changes the contents of the |
Behaviour
TIP may modify the INVITE traversing through from A to B, and may modify responses from B to A.
Header manipulation behaviour
| SIP Operation | TIPActive | Originating User TIP Override Category | Action(s) |
|---|---|---|---|
|
No |
N/A |
|
|
Yes |
N/A |
|
Response from B party |
Yes/No |
Yes |
|
Response from B party |
No |
No |
|
Response from B party |
Yes |
No |
|
