Use Extended Tracer in features

Updated Sentinel to use of Extended Tracer Interface (instead of Tracer) in features (VOLTE-8308).


Improved support for multiple home PLMN IDs

Add support for multiple home PLMN IDs spanning multiple MCCs, using the PLMN ID Analyser (VOLTE-7379). The configuration of home MCCs and MNCs has been removed from SipSentinelConfiguration, see the PLMN ID Analyser documentation for more details.


Support for Ro and Rf Failover

Add support for Ro and Rf failover to Sentinel SIP (PRD-1070). This includes:

  • Arming of various charging timers in redundant mode, if the session is replicated. This includes updates to the B2BUA SCUR features.

  • Arming of Session Refresh timers in redundant mode, if the session is replicated.

  • A new SIP Leg Manager API for proxying of requests inside the cluster

  • Updates to the ExternalSessionTracking feature so that it is capable of tracking Ro Dialogs in addition to SIP dialogs, as part of Ro session replication support.

  • Updates to the ExternalSessionTracking feature so that tracked dialogs are linked to the Sentinel Session’s Convergence Name.

  • Updates to the Interim CDR feature to allow Diameter Rf Accounting Requests to continue on the same Rf session after a failover.

  • Updates to the SCCSendRequestToAnchor and MMTelSTODTriggerAnchor features to proxy within the cluster or adopt the session if the original owning node has failed.

  • Use of the new Rhino 2.6.2 KV store replicated storage mode with session persistence initiated at a defined call point, from initial request to ACK SIP Session Replication Diameter Credit-Control Fault Tolerance.

Replacement of Sh Cache RA by Sh Cache Microservice

The Sh Cache RA has been removed, and the Sentinel products now use the Sh Cache Microservice 1.0.0.x series.

Vertical Service Codes

Support for Location Based Dialling

A new feature and accompanying provisioning tool have been added to support location based dialling, i.e. retargeting based on the cell tower the subscriber is currently connected to. Destination numbers are stored in Cassandra and configured through a provisioning tool provided with the sdk. See Location Based Dialling for details on how to configure this functionality.

PSAP Callback

Added support for disabling features that could potentially block calls on callbacks from emergency services. This functionality is disabled by default. To enable it, please see the MMTel Determine PSAP Callback feature documentation.

Operator Specific Barring Rule Based Retargeting

The profile table for specifying Operator Specific Barring rules has been substantially reworked. The table itself has been renamed from MMTelOdbOperatorSpecificTypesConfigProfileTable to MMTelOdbOperatorSpecificTypeRuleProfileTable. Previously each profile corresponded to a Sentinel Selection Key and had four fields, each containing the XML definition for one of the four possible operator specific rules. This has been changed so that now each profile corresponds to a single operator specific rule (still prefixed with a selection key). Each rule now has several associated config options on its profile. See How to Provision the Operator Specific Barring Rules for details about the fields each profile contains. Provisioning for Operator Specific Barring rules can now be done from the MMTelOCB and MMTelICB feature configuration pages.

The feature statistics for the MMTelOCB feature have changed due to behaviour changes required for this functionality, see MMTelOCB Statistics.

SCC Common Util Library

The SCC Common Util library contained helper methods for extracting digits from SIP and Tel URIs. Its functionality has been moved to the sentinel-volte-spi with the helper methods now found on the VolteFeatureUtil class. The scc-common-util module has been removed.

The an RA link name for the sis-in RA has been changed from sentinel-sis-in-hlrsubscriberdata has been changed to sentinel-sis-in-hlr. This change reflects the fact that the MAP event handler that uses it, is now employed by features other than the HLR Subscriber Data Lookup feature. Any feature that was using the old link name will need to be updated.


Removed APIs, Classes, Features, and Configuration

The following session state fields have been deprecated in Sentinel SIP:

  • EarlyMediaAnnouncementQueue in SipPlayAnnouncementFeature.

    • Use EarlyMediaAnnouncementInfoQueue instead to play early media announcements.

    • Use EarlyMediaAnnouncementInProgress to check whether an early media announcement is in progress.

  • MidCallAnnouncementID, MidCallAnnouncementQueue, PAShouldEndSessionWhenFinished, and MidCallAnnouncementPlayedParty in MidCallPlayAnnouncementFeature.

    • Use MidCallAnnouncementInfoQueue and MidCallEndSessionWithAnnouncement to play mid-call announcements.

    • Use MidCallAnnouncementInProgress to check whether a mid-call announcement is in progress.

External Session Tracking

There have been major changes to the way external session tracking is handled. The following features have been removed from Sentinel VoLTE:

  • TrackSessionPreAnswer

  • TrackSessionClearForks

  • TrackSessionRefresh

  • DeleteTrackedSession

Along with their associated modules:

  • track-session-pre-answer-feature

  • track-session-clear-forks-feature

  • track-session-refresh-feature

  • delete-tracked-session-feature

  • external-session-tracking-event-handler

The external-session-tracking-library has been renamed to be the access-leg-tracking-library. All occurrences of external-session and ExternalSession in this library (classes, methods, properties etc.) have also been changed to access-leg and AccessLeg respectively.

The external-session-tracking RA entity has been renamed to cassandra-general, as Session Tracking has been re-worked. Custom features that used this RA entity for Cassandra queries should now use the cassandra-general RA entity instead.

An example of an annotation change is:

        featureName = MMTelECTFeature.NAME,
        componentName = "@component.name@",
        featureVendor = "@component.vendor@",
        featureVersion = "@component.version@",
        featureGroup = SentinelFeature.SIP_FEATURE_GROUP,
        configurationReader = @ConfigurationReader(
                readerInterface = MMTelECTConfigReader.class,
                readerClass = MMTelECTConfigProfileReader.class
        raProviderJndiNames = {
                // old - prior to 2.8.0
                // new - post 2.8.0 below
        // other annotation lines

See the Session Tracking page for details of the new session tracking system.

Inter-node Communication

The VoLTESharedConfigProfileTable has been removed, along with its associated modules: volte-shared-config-profile and volte-shared-config-profile-reader-sbb-part.

The URIs previously held on this table is now automatically derived from SIS SIP network interface responsible for inter-node communication. * If there is only one network interface configured on the SIP SIS RA then it will be automatically used for inter-node communication. * If there are multiple network interfaces configured, one of them will need to be nominated for inter-node communication using the InterNodeInterfaceName RA config property.

Module Naming Consistency

All of the modules and classes that had volte-sentinel or VolteSentinel in their names have been renamed to sentinel-volte and SentinelVolte.

Service Renaming

The VoLTE services have been renamed to align with the module renaming. Previously volte.sentinel.sip and volte.sentinel.ss7 are now sentinel.volte.sip and sentinel.volte.ss7 respectively.

Obsolete Components

The following obsolete components have been removed from Sentinel VoLTE:

  • Use of HssCacheBasedSubscriberIdentitiesSbb.isReRegister()

  • VolteSipLegacyCdr feature and volte-sentinel-legacy-cdr-format.

  • Remove modules living in volte-sentinel-legacy-modules

    • mmtel-tip-profile

    • mmtel-tir-profile

    • scc-determine-session-type-profile

    • volte-common-session-state-library

    • volte-common-util-library

Multiple deployment options

The Sentinel VoLTE SDK now allows deployments for:

  • SCC-AS only,

  • MMTel-AS only,

  • CDMA vs GSM variations of both of the above, and

  • a new "dev deploy" to be used when building a new SIP AS

Previous page Next page