This feature replaces the undisclosed identity with the shared identity for an originating call from a companion device where such hiding has been requested .
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 |
Yes |
Originating |
|
Yes |
Yes |
Stateless |
POJO |
Feature Configuration
The profiles within the HideUndisclosedIdentityConfigProfileTable
are selected using the SentinelSelectionKey
and has the following field:
Parameter | Type | Description |
---|---|---|
HideUndisclosedIdentities |
boolean |
Whether undisclosed indentities should be hidden |
Session Input Variables
Session State variable name | Type | Comments |
---|---|---|
SentinelSelectionKey |
SentinelSelectionKey |
Determines which configuration to use |
HideUndisclosedIdentities |
boolean |
|
SharedIdentitySip |
URI |
Used to replace undisclosed |
SharedIdentityTel |
URI |
Used to replace undisclosed |
Statistics
HideUndisclosedIdentity 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 → HideUndisclosedIdentity
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.HideUndisclosedIdentity"
Statistic | 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 |
HideUndisclosedIdentities |
a message is modified to hide the undisclosed identity |
SharedIdentitySip |
a message header address is replaced with the SIP shared identity |
SharedIdentityTel |
a message header address is replaced with the TEL shared identity |
UnsupportedExecutionPoint |
the feature is called from an unsupported execution point |
Behaviour
-
If the call type is not mobile originating then the feature finishes with no further processing.
-
If the session state field
HideUndisclosedIdentities
isfalse
then the feature finishes with no further processing. -
If neither
SharedIdentitySip
orSharedIdentityTel
session state fields are defined, the feature fails to execute. -
The
HideUndisclosedIdentityConfigProfileTable
profile table is read using the current selection key, and if itsHideUndisclosedIdentities
field isfalse
, then the feature finishes with no further processing. -
When called from the
SipAccess_SubscriberCheck
execution point, thefrom
header in the outgoing message is modified.-
If the header value is a SIP URI, and
SharedIdentitySip
is defined, or ifSharedIdentityTel
is not defined, the header value address is replaced withSharedIdentitySip
-
Otherwise the header value address is replaced with
SharedIdentityTel
-
-
In the outgoing message, the
P-Asserted-Identity
header is modified.-
For each address in the header value
-
If the address is a SIP URI, and
SharedIdentitySip
is defined, the header address is replaced withSharedIdentitySip
-
If the address is a Tel URI, and
SharedIdentityTel
is defined, the header address is replaced withSharedIdentityTel
-
-